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

GaurangTandon left a comment (w3c/editing#200)

Hi folks! Apologies for reviving this old thread. I see that this was the latest resolution on `execCommand` behavior for browser extensions ([comment link](https://github.com/w3c/editing/issues/200#issuecomment-578097441)):

> In case of browser plugins/extensions: We agree that execCommand should cause a beforeinput event and that this beforeinput event should use the regular inputTypes in case there are is one corresponding to the command and otherwise an empty string. This should be added to the execCommand spec by means of a PR1.

It seems to me that Firefox has shipped this change ([Bug 1618091](https://bugzilla.mozilla.org/show_bug.cgi?id=1618091)), whereas Chrome still has the old behavior. Is there a tracking issue in Chrome for this? The change would be very helpful for my use case, for the reasons that were already discussed. So I'm looking forward to it. Thanks!

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

Message ID: <w3c/editing/issues/200/2690527364@github.com>