New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should parts of Input Events level 2 be moved to level 1? #275
Comments
@alexkeng and @snianu do you know if the change was intentional? If so, +1 to @johanneswilm proposal to update the spec. |
Yes, even if it was not intentional I am wondering if this will be reverted now that it has shipped like this in Chromium already? The current behavior is the same as Webkit. |
FYI @mustaqahmed as for the current owner of the code base. |
ping @mustaqahmed |
Ok, I've done some digging. In the bug, there is an ask to make Chrome comply with Level 2 spec. I would agree with @johanneswilm 's analysis and don't think this was accidental nor that it will be reverted. I support making the change to the spec. |
I also support the change. Thanks @gked for covering my absence. |
@johanneswilm proposing to close this issue. Thoughts? |
I agree. Let's close it.
…On Wed, Mar 10, 2021, 00:43 Grisha Lyukshin ***@***.***> wrote:
@johanneswilm <https://github.com/johanneswilm> proposing to close this
issue. Thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#275 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAERMOFTGNYN7WIVN35J4RDTC2QCZANCNFSM4TUYO6EQ>
.
|
When we created level 1 and 2 of Input Events it was because the Chromium team found it impossible to make some beforeinput events cancelable in what was then the unified Input Events spec and which is now known as level 2. Particularly any inputType that added or removed content was to not be cancelable in Chromium. So we made a level 1 that did not specify that they were cancelable and a level 2 that specified that almost all beforeinput events were cancelable.
However, now it seems like Chromium currently actually does allow a lot (all?) of those that are undefined in level 1 to be cancelable. The question is then - if both Chromium and Webkit have implemented this part of level 2 and noone has implemented just level 1, should we move this from level 2 to level 1 so that the delta between the two is smaller?
See https://jsfiddle.net/yv1sg2td/7/
See also w3c/input-events#115
The text was updated successfully, but these errors were encountered: