- From: Ojan Vafai <ojan@chromium.org>
- Date: Mon, 22 Oct 2012 18:32:02 -0700
- To: Ian Hickson <ian@hixie.ch>
- Cc: whatwg <whatwg@lists.whatwg.org>, Aryeh Gregor <ayg@aryeh.name>
On Sat, Oct 20, 2012 at 4:55 PM, Ian Hickson <ian@hixie.ch> wrote: > On Sat, 20 Oct 2012, Aryeh Gregor wrote: > > > > On Thu, Oct 18, 2012 at 1:23 AM, Ian Hickson <ian@hixie.ch> wrote: > > > Incidentally, it seems to use a WebKit-specific "plaintext-only" value. > > > Should we spec that? Aryeh? It's filed as: > > > > > > https://www.w3.org/Bugs/Public/show_bug.cgi?id=14554 > > > > > > If this should involve changes to HTML, let me know. > > > > In principle, yes, this should be specced. In practice, it would > > require extensive changes to the editing spec and a lot of careful > > thinking, and no one is really working on editing implementations > > anyway. Gecko's editor code is in maintenance mode, I haven't received > > a single piece of feedback ever about editing from IE or Opera people, > > and WebKit is the one that already implements the feature, so I don't > > see the effort as being worth the time spent right now. (I did receive > > feedback from Opera about selection, but not editing as far as I > > remember.) > > > > The same goes for any other proposed editing spec features. When I see > > people actually implementing the existing spec, that's when it will make > > sense for me to spend more of my time adding more stuff to it. Until > > then, I might fix bugs, but that's it. > > Sounds reasonable. > FWIW, when I discussed this with Mozilla folk a couple years ago, the only sticking point was what hitting enter should should in a plaintext-only region. In WebKit, it inserts a <br>. Some people thought it should insert a '\n' and/or should based what it inserts off of the CSS whitespace property. Never really came up with a resolution to that question.
Received on Tuesday, 23 October 2012 01:32:51 UTC