15527 2012-01-11 20:52:51 +0000 Allow div (and maybe br) as a paragraph separator 2012-02-24 20:48:32 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - HTML Editing APIs unspecified All All RESOLVED FIXED P2 enhancement --- 1 ayg ayg ehsan mike ojan public-webapps rniwa zcorpan sideshowbarker+html-editing-api oldest_to_newest 62574 0 ayg 2012-01-11 20:52:51 +0000 See discussion: http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/0045.html and responses. 64560 1 ayg 2012-02-24 17:47:13 +0000 Okay, so I'm going to implement this now. I'll make it a command called defaultBlock, which will only take values "div" and "p". I've seen no good use-cases yet for br over div, and a br option would make things significantly more complicated. Really I'd like to fix bug 15522 first (allow execCommand on Element), so that this command can be scoped. But I don't view that as a blocker, and it would be added complication, so I won't. (I'd have to fix about a million references to "the context object".) This will probably double the number of tests that get run. :( 64565 2 rniwa 2012-02-24 18:45:18 +0000 Can we use defaultParagraphSeparator or something along that line? We have both InsertParagraph and InsertLineBreak and this command should only change what the former command inserts. defaultBlock sounds too generic to me. 64566 3 ayg 2012-02-24 18:54:58 +0000 Okay. No objection from me. 64567 4 rniwa 2012-02-24 18:56:46 +0000 (In reply to comment #1) > Really I'd like to fix bug 15522 first (allow execCommand on Element), so that > this command can be scoped. But I don't view that as a blocker, and it would > be added complication, so I won't. (I'd have to fix about a million references > to "the context object".) Yeah, fixing that bug will be great. 64568 5 ayg 2012-02-24 19:27:03 +0000 Tell you what: implement these two spec changes, and then you can ask me for more changes. :) 64574 6 ayg 2012-02-24 20:48:32 +0000 Fixed: http://dvcs.w3.org/hg/editing/rev/b35a81679b49