W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

RE: [editing] defaultParagraphSeparator

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Sat, 9 Feb 2013 01:11:41 +0000
To: Pablo Flouret <pablof@motorola.com>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <d6180e3968044fe2a141209ba6add53d@BLUPR03MB033.namprd03.prod.outlook.com>
± From: Pablo Flouret [mailto:pablof@motorola.com]
± Sent: Monday, February 4, 2013 12:47 PM
± 
± On Mon, 04 Feb 2013 11:59:46 -0800, Alex Mogilevsky <alexmog@microsoft.com>
± 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


I can't find any documentation for any of the implementations, perhaps you could answer if the following is true:

* The command name is "defaultParagraphSeparator", unprefixed 
* Argument is case insensitive
* The only available options are "P" and "DIV"
* Default is "P"

Is that correct?

Thanks
Alex
Received on Saturday, 9 February 2013 01:13:10 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT