Re: [w3c/editing] INPUT/TEXTAREA should support subset of execCommand (#160)

@eranroz Right, but the question behind this is: do we want the browser to provide this global undo stack or not. Currently it's hurting all the richtext editors, including the Wikimedia one and those created by browser makers. Browser priorities are generally not in favor of text editing because they have so many other things to look at. I see your bug report is from 2011. In a choice between either:

A) getting more of this global undo stack added to the browsers, and trying to be smart and somehow guess what happens with script-added content whereby another 15 bugs are added and the browser makers will wait another 5-7 years before browser makers again have the resources to look at editing again, and

B) getting an option to opt out of the global undo stack for an individual elements and so that you can then program your own undo system without interference from the browser,

I think B will be the clear choice for most JS editors.  Every richtext editor has programmed their own undo system anyway.

That being said, if what Firefox will add to input and textarea is completely isolated within each element, then I don't think it's problematic for them to add it.

-- 
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/issues/160#issuecomment-395816760