-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Added a global event handler for beforeinput #4530
Conversation
Also imported the input event from the UI events specification, since that one defines it. Fixed whatwg#4526
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
heads-up @whatwg/documentation |
Documentation potential need recorded at https://trello.com/c/aBs1o6Pg/86-dom-general-enhancements-fx-67 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, so what remains here:
- Implementer interest if not implemented.
- Implementer bugs if not implemented.
- WPT coverage. (I guess we get some automatically through IDL, maybe enough?)
@annevk - and verifying my participation. Looks like WebKit added it already, without adding it to the standard - Chromium issue - https://bugs.chromium.org/p/chromium/issues/detail?id=947408 An intention by Mozilla to add it when they implement |
@annevk - regarding tests, yes, I assumed IDLs are automatically tested. |
Ah yeah, it should be a content attribute as well. |
@annevk - I will add it in the UTC+2 evening. Anything else left other than the content attribute and verifying my participation? |
No, I think we're good then, thanks! I'll verify you now. |
@annevk -
Unrelated, but why does I added the content attribute. One more thing, is adding my name to the acknowledgement section mandatory? I assumed it was, so I added, but I generally rather not if it is possible. |
I'm not sure this should be verified, as I don't believe signing a contract using a pseudonym is viable legally... |
@domenic - Google was fine with it, jQuery was fine with it (they did consult first) and maybe a few more I signed (RavenDB was not fine but only because they required an exact address and phone number which I am not willing to provide). But if you have an issue with that, I hereby release all rights for my change and you or anyone else is welcome to take it as their own, no credit needed. |
@domenic I've verified other pseudonym-like names. Also, without ID verification of some kind many others could be pseudonyms too? |
@phistuck adding your name to the Acknowledgments section is optional, feel free to remove it. |
@annevk - done. Thank you for the review, everyone. |
@annevk and @domenic - from the agreement status page -
This is preventing a pull request from being accepted for three months. It would be great if you expedited the process. |
We are blocked on confirmation from the SG as to whether pseudonyms are acceptable. This is out of our hands. We can close the PR if that's preferable to you. |
Any update on this and #4526? Seems a shame to not be able to land the PRs over names vs. pseudonyms. Can we land this under a different name, or does a fresh PR need to be made? |
A fresh PR is probably the best way forward. |
@mfreed7 - sure, go for it, let me know when you have and I will close this one. |
Also imported the input event from the UI events specifications, since that one defines it. Fixes whatwg#4526 (This PR is directly pulled from whatwg#4530, which can't land due to IP issues.) (This PR is a replacement for whatwg#6743, which I neglected for too long.)
Also imported the input event from the UI events
specifications, since that one defines it.
Fixed #4526
💥 Error: Wattsi server error 💥
PR Preview failed to build. (Last tried on Jan 15, 2021, 7:59 AM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 Wattsi Server - Wattsi Server is the web service used to build the WHATWG HTML spec.
🔗 Related URL
If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.