-
Notifications
You must be signed in to change notification settings - Fork 371
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
Event path trimming should only happen for mouseover and mouseout #330
Comments
If we (in some off chance) were to keep the currently spec'ed behavior, then the following text belongs to an informative note, not a normative text since this trimming behavior applies to all trusted events.
|
Doing this flag-based does seem more sane. Since it would actually explain what is going on. (Where did I hear that before?) |
Yeah, I think I like the flag-based approach best. cc @hober @othermaciej |
This is the original bug for the current spec. https://www.w3.org/Bugs/Public/show_bug.cgi?id=20017 The flag-based approach is okay to me. |
An alternative to specify a boolean would be to specify a node at which the propagation stops: e.g. |
I'm not sure how we can resolve this issue. Does someone have a preference? |
My preference is to add a flag instead of treating trusted events differently since the rationale for trimming the event path is semantically nothing to do with whether event should be trusted or not. |
|
I think we agreed on using the flag. Let me update the spec so that it uses the flag in relevant sections. Note that the flag name is not finalized. It could change if we find a better name. |
It's very strange for the event path trimming algorithm to apply trusted events with
relatedTarget
.Why don't we just do this for all
mouseover
andmouseout
events and nothing else. Alternatively, we can add a new constructor option to MouseEvent's init dictionary likestopsAtLowestCommonShadowRoot
to explicitly set this behavior so that authors can adjust it. If we did the latter, we'd just make UAs create MouseEvents with that flag set totrue
when firing trusted events.@travisleithead @annevk: any opinions?
The text was updated successfully, but these errors were encountered: