Re: [w3c/editing] Change default paragraph separator from <p> to <div> (#146)

> Do editors all override hitting Return, Backspace, etc.?

Those involve taking apart and merging paragraphs, so I cannot really imagine how one would create an editor without doing that. At the very least one will need to monitor what the browser does and then adjust if needed. Not sure what @Reinmar think, but I would say for those just try to be as similar as Chrome given that that is the currently most popular browser on those. Given that the Chrome team says they are not going to fix this, the best we can hope for is that all browsers will be broken in the same or a similar way.

> If there are any Firefox bugs you think are particularly worthwhile to fix, please file a few and CC me (or give me a link if you already did).

I linked to two bug reports @Reinmar and me filed in a 2014 ACM article [1]. My top priority bug for Firefox is the one mentioned above, and was filed in 2013 [2]. I can also see that @Reinmar has filed a number of issues in the period 2013-15 [3]. Most of that still seems current, but priorities may have shifted slightly on the part of JS editors due to the changes in how JS editors are operating nowadays. The top priority right now would really seem to be to get the beforeinput event implemented in Firefox in the same way that Chrome is currently implementing it. Or what would you say, @Reinmar?

[1] http://dl.acm.org/citation.cfm?id=2723154
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=873883
[3] https://www.google.com/search?q=Piotrek+Koszuli%C5%84ski&gws_rd=ssl#safe=off&q=piotrek+koszuli%C5%84ski+site:bugzilla.mozilla.org

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/pull/146#issuecomment-242434100