Re: [w3c/editing] [charter] execCommand spec should be in scope (Issue #432)

@zcorpan OK, and is someone from Mozilla willing to step forward as the maintainer and do you have a promise from a second browser engine to implement the execCommand spec? The reason I am asking is that other browser engines previously made it very clear that they would not make changes to their browsers based on what that a execCommand spec says, but that they may make changes if it can be shown that multiple other browser engines handle some case differently than they do. That's why we have had discussions about specific issues on Github or the mailing list over the last few years and some of those discussions have ended up with a change to the execCommand spec document.

As for evidence of work: If I recall correctly @masayuki-nakano / Mozilla proposed last year to work on a few things related to contenteditable that would also impact execCommand as part of the interop effort. This was accepted by other participants on the condition that what was going to be tested would be strictly limited to a few specific cases. 



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

Message ID: <w3c/editing/issues/432/1589096615@github.com>