Re: [w3c/editing] Should execCommand dispatch beforeinput or not? (#200)

@tszynalski JS is single threaded so of you insist on using execCommand internally in your editor app, in spite of our warnings against it, then you should still have no issue distinguishing a beforeinput event that was caused by execCommand in your own code from one that comes from user input. Just set some property like `this.executingCommand = true` somewhere in your code before you run the execCommand and then turn it off when you are done. Also, we should absolutely not encourage the usage of execCommand unless there is no alternative.

@masayuki-nakano Given the comment by @scottfr on Chrome preventing recursive execCommand, do you still feel there is a need to differentiate? Do you have another example where this will be relevant? 

-- 
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/200#issuecomment-575718386