[wp-trac] [WordPress Trac] #12423: Include Ace (or similar) as default code editor

[WordPress Trac]

#12423: Include Ace (or similar) as default code editor
-----------------------------+----------------------------
 Reporter:  scribu           |       Owner:  afercia
     Type:  feature request  |      Status:  assigned
 Priority:  normal           |   Milestone:  4.8
Component:  Editor           |     Version:  3.0
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  accessibility
-----------------------------+----------------------------

Comment (by FolioVision):

 Thanks for the links Luke. I particularly find useful Piotrek
 Koszuliński's essay [https://medium.com/content-uneditable
 /contenteditable-the-good-the-bad-and-the-ugly-261a38555e9c#.t8uf5ee0w
 ContentEditable — The Good, the Bad and the Ugly]. Wow those Medium URLs
 are hideous and unreliable: let's never do that to URLs with WordPress.
 Here's a simpler working link which brings up both articles and any new
 ones about [https://medium.com/content-
 uneditable/search?q=content%20editable ContentEditable].

 I found this section particularly relevant:

     ContentEditable is like JavaScript, only Douglas Crockford hasn’t
 written a book about it yet. But (like JavaScript) it also has its good
 parts (yeah, I know — the good/bad ratio is debatable). It’s amazing that
 adding one attribute to an HTML element enables typing, selection,
 keyboard navigation, spell checking, drag and drop, pasting, undo manager.
 That all of this is integrated with the OS, that such editor can be used
 with a screen reader or on a touchscreen device and that it’s well
 internationalised. Let’s focus on these good parts and forget the bad
 ones.
     Over the past years, while working on CKEditor I noticed that we were
 gradually replacing native features with our own implementations....It
 means that today CKEditor does not let the browser do anything to the
 content except handling typing, some deleting and that’s basically it. At
 the same time, it still uses the native selection system, keyboard
 navigation and other APIs such as those related to clipboard or focus
 management.

 What this suggests to me is that any good JS code editor will be
 sufficiently complex that just pasting in some screen reader functionality
 will result in a not particularly sharp pencil. We would really be better
 off building a dedicated code editor for screen readers into our new code
 editor.

 I would be very grateful if someone better versed in editing with a screen
 editor would **share the gold standard for code editing with a screen
 reader** so we could compare that ideal situation with where we are with
 the CodeMirror adaptation.

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