Re: [w3c/editing] Updated the intro material to better reflect the current status. (#302)

@njdjacobs As I stated before - it's entirely possible that a consensus can be formed around a different wording for that paragraph. It's just not clear that is the case. The current wording basically tells JS devs to stay away from execCommand if they expect it to work well across browsers. Your wording would take that notice away. If major new projects were to try to start creating a new execCommand based editor due to the changed notice and it turned out it doesn't work as well across browsers as you are saying, then that might put pressure on browser makers to shift their resources toward execCommand and thereby take away resources from other areas. The current wording was negotiated in a complex setting and so this is not a decision you and I can just take to change that notice now.

I really suggest for you to please either present your proposal at a call or as an email on the email list so that we really can have a real discussion on it. And if I understand you correctly, you have tested all aspects on all browsers and have checked that execCommand now work the exact same way on all browsers. If you have done that, then there should be no problem calling yourself an "expert" on the matter either. 

-- 
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/302#issuecomment-887226828