Make WordPress Core

Opened 10 years ago

Closed 10 years ago

#28881 closed enhancement (duplicate)

HTML structure bar not floating in TinyMCE in 4.0

Reported by: hardeepasrani's profile hardeepasrani Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.0
Component: TinyMCE Keywords: needs-patch
Focuses: ui Cc:

Description

I'm trying out WordPress 4.0 Beta from few days and found little, but frustrating bug in the all new floating TinyMCE editor.

There is a bar in the bottom of TinyMCE which shows

div » div » p

type HTML structure - not sure what to call that.

This is still in the floating TinyMCE - but with a small issue

When there's a lot of text in the TinyMCE, and you scroll back to top or anywhere, it disappears. It only appears at the bottom of the bar.

In short, that structure bar should also float with the editor. Attaching a photo to easily explain what I'm trying to say here :)

Attachments (1)

Floating TinyMCE.png (65.6 KB) - added by hardeepasrani 10 years ago.

Download all attachments as: .zip

Change History (8)

#1 @hardeepasrani
10 years ago

  • Summary changed from HTML structure breadcrumb gone from floating TinyMCE in 4.0 to HTML structure bar not floating in TinyMCE in 4.0

#2 @iseulde
10 years ago

  • Milestone changed from Awaiting Review to 4.0

That's intentional... It should probably pin too, but that's another pinned toolbar added to the stack. I think we should completely hide it by default, I'm not sure if it's that useful for most WordPress users.

Related: #21605.

#3 @hardeepasrani
10 years ago

I'm not a visual editor guy, but I really find it useful whenever I'm using the visual editor.

Hiding it won't hurt me too much :)

This ticket was mentioned in IRC in #wordpress-dev by DrewAPicture. View the logs.


10 years ago

#5 @DrewAPicture
10 years ago

  • Milestone changed from 4.0 to Future Release

No patch and no consensus here on whether to punt, merge the bottom toolbars or just plain hide it. Punting.

Version 0, edited 10 years ago by DrewAPicture (next)

#6 @hardeepasrani
10 years ago

  • Keywords needs-patch added
  • Type changed from defect (bug) to enhancement

I'm not an amazing guy when it comes to coding, but you can tell me where the code of this bar is located so I can try my hands a little bit - just for learning ;)

#7 @helen
10 years ago

  • Milestone Future Release deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Duplicate of #29293.

Looks like this got done after all.

Note: See TracTickets for help on using tickets.