[Webkit-unassigned] [Bug 57149] Ending a list in contentEditable/designMode with enter produces a div

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Aug 19 09:03:16 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=57149


Aryeh Gregor <ayg at aryeh.name> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |ayg at aryeh.name
     Ever Confirmed|0                           |1




--- Comment #2 from Aryeh Gregor <ayg at aryeh.name>  2011-08-19 09:03:16 PST ---
The result of that discussion was that we should converge on the behavior of IE/Opera, which is to use <p>'s; and to wrap every line in a <p>, even the first (see bug 31678).  That's what I wrote in the spec:

http://aryeh.name/spec/editing/editing.html#the-insertparagraph-command

In practice, this is one of the most annoying interop issues with contenteditable: IE/Opera uses <p>, Gecko uses <br>, WebKit uses <div>.  The big issue here is that this affects even authors who don't use execCommand() at all, which lots of authors don't because it's too unreliable.  They still have to use contenteditable, and this is one of the biggest differences between browsers for contenteditable.  They also behave differently for delete and so on, but this difference affects every contenteditable region where the user ever pressed Enter, which is almost all of them.

So IMO, this would be a good thing to prioritize.  That way at least browsers would produce similar markup for the case where the user just types text in contenteditable without running execCommand().

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list