[wp-trac] [WordPress Trac] #27013: Contain scrolling inside the editor

[WordPress Trac]

#27013: Contain scrolling inside the editor
----------------------------+-----------------------
 Reporter:  azaozz          |       Owner:  azaozz
     Type:  task (blessed)  |      Status:  reopened
 Priority:  normal          |   Milestone:  3.9
Component:  TinyMCE         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  needs-testing   |     Focuses:  ui
----------------------------+-----------------------

Comment (by markjaquith):

 I chatted more with Nacin last night about my last bullet point. Here's
 the idea, in more detail:

 1. Editor height auto-expands/contracts to fit content.
 2. Editor toolbar stops moving up when it hits the admin toolbar (pins to
 top, content scrolls under it). You always have access to the editor
 toolbar.
 3. Editor footer is pinned at the bottom of the screen if there is more
 content below. So you always have access to the editor footer.
 4. If you reach the bottom and keep scrolling and the footer is in danger
 of touching the header, the header should unpin and scroll off the screen
 (for the case where you're scrolling past content to get to meta boxes
 below it).
 5. For long posts, there are contextual "jump to top" and "jump to bottom"
 buttons (maybe they just show if you are scrolling in that direction, and
 there are more than 800 pixels to go in that direction).
 6. The publish box (when in the sidebar) pins to the top as it is about to
 scroll off the page, and then accordions to just display the top and
 bottom of it (the main action items) as the page scrolls further.
 7. Bonus idea: If all of your sidebar meta boxes fit in the browser
 height, they should be pinned.

 WHY:

 1. Nested scroll areas are a terrible interaction paradigm.
 2. Anything we do to fix that isn't going to quite feel right (a pause or
 a stickiness makes it seem like something is broken or CPU-constrained
 somehow).
 3. Content is king. That we hide your content so we can display a "Custom
 Fields" metabox is, frankly, embarrassing.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/27013#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform