Make WordPress Core

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#30961 closed defect (bug) (fixed)

editor expand: TinyMCE statusbar not hidden when kitchensink is off and editor at minimum height

Reported by: iseulde's profile iseulde Owned by: azaozz's profile azaozz
Milestone: 4.2 Priority: normal
Severity: minor Version: 4.1
Component: Editor Keywords: has-patch
Focuses: javascript, administration Cc:

Description

With kitchensink *off*:

Editor starts with both the word count and TinyMCE status bar (with the path).
When it gets larger the TinyMCE status bar disappears.
When it shrinks to minimum height again it pops up.

When kitchensink is off, the TinyMCE status bar should always be hidden.

Attachments (1)

30961.patch (1019 bytes) - added by iseulde 11 years ago.

Download all attachments as: .zip

Change History (8)

@iseulde
11 years ago

#1 @iseulde
11 years ago

  • Keywords has-patch added

#2 @azaozz
11 years ago

  • Owner set to azaozz
  • Resolution set to fixed
  • Status changed from new to closed

In 31118:

TinyMCE editor-expand: when kitchensink is off hide the statusbar on loading, and when the editor is shorter then the viewport. Props avryl, fixes #30961.

#3 @azaozz
11 years ago

  • Severity changed from normal to minor

Not sure if this should go in 4.1.1, too minor?

#4 @helen
11 years ago

  • Keywords fixed-major added
  • Resolution fixed deleted
  • Status changed from closed to reopened

#5 @dd32
11 years ago

  • Keywords fixed-major removed
  • Milestone changed from 4.1.1 to 4.2
  • Resolution set to fixed
  • Status changed from reopened to closed

Seems like a small enough edgecase to skip 4.1 inclusion to me.

Last edited 11 years ago by dd32 (previous) (diff)

#6 @iseulde
11 years ago

I notice this every time I use a 4.1 install. If you start a new post, you'll see the TinyMCE path bar at the bottom of the editor. As soon as you start typing and the editor becomes larger, the bar disappears. Pretty weird.

#7 @dd32
11 years ago

The comment was actually intended for a different ticket, but you're right, any developer once they notice it is going to keep noticing it (especially one who has worked on that feature).

I still really don't think it's going to be noticed, or cared for, by any regular users though. I'd be highly surprised if most people even use that bar.

Note: See TracTickets for help on using tickets.