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

>>> I think such a prefix would break the usecase described by @scottfr above.

>> I meant that if the caller of execCommand is browser itself or part of browser (i.e., addons), such prefix shouldn't be added because it looks like a user's intention from point of view of web apps. So, I meant that when execCommand is called by web contents, adding prefix

> In that case I am OK with your suggestion. Some legacy apps may use execCommand directly in the app, but those apps then don't need to also use beforeinput events, at least not in the non-prefixed version.

These seams reasonable to me.

> editor.addEventListener("beforeinput", event => {...});

Not to diminish the compatibility concerns, but as an aside, if 'beforeinput' was added to execCommand without any changes to the inputType, I think this specific example would still happen continue to work correctly in Chrome as they bail when they detect recursive execCommand command calls: (https://source.chromium.org/chromium/chromium/src/+/master:third_party/blink/renderer/core/editing/commands/document_exec_command.cc;l=75). So I think the first execCommand would execute and then the second would fail. (Maybe this recursion behavior is worth clarifying too or opening an issue on?)

-- 
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-575241816