[wp-trac] [WordPress Trac] #28328: Focus on editing, while editing

WordPress Trac noreply at wordpress.org
Sun Aug 10 02:10:33 UTC 2014


#28328: Focus on editing, while editing
-------------------------+-------------------------------------------------
 Reporter:  markjaquith  |       Owner:
     Type:  task         |      Status:  new
  (blessed)              |   Milestone:  4.0
 Priority:  high         |     Version:
Component:  Editor       |  Resolution:
 Severity:  critical     |     Focuses:  ui, accessibility, javascript,
 Keywords:  needs-patch  |  administration
-------------------------+-------------------------------------------------
Changes (by helen):

 * keywords:  ui-feedback ux-feedback needs-testing has-patch => needs-patch
 * severity:  normal => critical


Comment:

 I think there are a few things we should do/try if we are to keep this in
 4.0. I discussed this with markjaquith and nacin in person at WCNYC to
 general agreement.

 1. Do not pin the toolbar when we are at the minimum height. Right now
 when you have no text or just a couple lines, the top toolbar will pin and
 you can scroll the content off the screen underneath it, which makes no
 sense. The editor should just start shorter, then.
 2. Pin the side metaboxes (when they're on the side) so they never go off
 screen completely. When you scroll back up, also scroll up the metaboxes.
 It does mean that two parts of the screen scroll kind of differently. This
 might not work well in practice, but we need to at least try it.
 3. (lower priority) Some kind of jump to metaboxes / after content link.
 This needs some careful language consideration, and may be weird in
 practice. But again, need to try it.

 We also generally need to be deliberate about making sure we've considered
 varying use cases, whether we do something to the feature that
 accommodates or we rely on the ability to turn it off. As it is, we know
 that it's very frustrating when you have long content, and when there are
 multiple editors on a screen, e.g. in multilingual/localized content
 situations. There is also that you were previously able to configure your
 editor height and we are now essentially dropping it by default - not a
 bad thing, but certainly understandable that it may cause some confusion.

 Finally, that screen option is awkward - looks like it's just kind of
 hanging out, and not sure the language is very meaningful.

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


More information about the wp-trac mailing list