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
move beforeinput event and input event from HTMLElement to Element
#30288
Conversation
|
Thanks @skyclouds2001 - taking a look shortly |
|
Searching through other content brings up these: content/files/en-us/web/svg/attribute/end/index.md Lines 70 to 71 in 00a2f5f
Could we fix it in this PR, also? Those are the last ones I can find in other docs. |
|
honestly, I check the standard again, and notice that other event types in UI Events spec that say its target can be element, their documentations are written in I check these events via event handle property (like reference to Touch Events and Pointer Events, their event property handler are defined in also reference to TypeScript DOM definition file, which defines the so I guess a better solution is to move |
beforeinput event and input event from HTMLElement from Element
beforeinput event and input event from HTMLElement from Elementbeforeinput event and input event from HTMLElement to Element
From the spec:
This makes sense to me. Note that if we move, it will need to also be moved in BCD:
@queengooborg any thoughts on this? |
|
BCD places events based upon where the events are defined in the spec, rather than the event handlers -- so, this change makes sense to me, yes. |
|
This pull request has merge conflicts that must be resolved before it can be merged. |
|
This pull request has merge conflicts that must be resolved before it can be merged. |
|
This pull request has merge conflicts that must be resolved before it can be merged. |
|
This pull request has merge conflicts that must be resolved before it can be merged. |
|
Looking great, and I see the corresponding BCD is done, so I think we can merge shortly. Is it correct to say there are some minor leftovers of (
|
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.
After the BCD has landed in mdn/browser-compat-data#21640, leaving +1 with some comments for flaws that we can fix here. We can merge after cleaning these up if you like
Thank you!
fixed! |
|
Looking great, let's merge 🚢 |
* zh-cn: sync translated content * move beforeinput event and input event from HTMLElement to Element ref: mdn/content#30288 * Remove mobile guides and redirect to responsive design guide ref: mdn/content#31540 --------- Co-authored-by: Allo <yin199909@aliyun.com>
…ment` (mdn#30288) * fix link * add * revert· * move files * update link * HTMLElement/input_event to Element/input_event * update * fix links --------- Co-authored-by: Brian Thomas Smith <brian@smith.berlin>
…ment` (mdn#30288) * fix link * add * revert· * move files * update link * HTMLElement/input_event to Element/input_event * update * fix links --------- Co-authored-by: Brian Thomas Smith <brian@smith.berlin>
Description
in UI Events, the
beforeinputevent andinputevent has failed link, this is because the two events' documentation is only written underHTMLElementnot underElementand other event types (like mouse events) in the standard that target to element do documented in
Elementrather thenHTMLElement(also, interstingly, as I check via event handle property (like
oninput), they are available onHTMLElementSVGElementorMathMLElement, andWindoworDocument, but not available onElement, this also happens to other UI Events, this behavior is similar to Pointer Events and Touch Events)also add
Element: auxclickandElement: contextmenuinto group data of UI Events, see https://w3c.github.io/uievents/Motivation
Additional details
Related issues and pull requests