± From: Pablo Flouret [mailto:[email protected]] ± Sent: Monday, February 4, 2013 12:47 PM ± ± On Mon, 04 Feb 2013 11:59:46 -0800, Alex Mogilevsky <[email protected]> ± wrote: ± ± > There was a discussion here a while ago on desired default behavior ± > for Enter in contenteditable and options for ± > execCommand("defaultParagraphSeparator"): ± > http://lists.w3.org/Archives/Public/public-whatwg-archive/2011May/thre ± > ad.html#msg171 ± > ± > Did it ever get to consensus? Or is there new thinking on how that ± > should work? ± ± I implemented this in Opera and WebKit[1], can't really tell from the ± bugzilla bug if it's in firefox too[2], but i think they were on board as ± well. ± ± [1] https://bugs.webkit.org/show_bug.cgi?id=59961 ± [2] https://bugzilla.mozilla.org/show_bug.cgi?id=748303
The "Editing API" document flags "defaultParagraphSeparator" as having issues, some are mentioned in the document and more raised in the discussion. Such as * default value (currently 'p', but not consistent in implementations) * default styles (if 'p' is default, it adds default 1em margin before first line, which most people consider undesirable) * when should Enter insert a line break instead of block (e.g. when inside <pre>)? * can/should the default block be set per editable area and how? * why only 'p' and 'div'? If there is a chance to settle on what's right for any of these, it would be awesome. Alex [1] https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#the-defaultparagraphseparator-command
