Stop propagating inertness into nested browsing contexts #7606
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Firefox doesn't propagate it. Blink does, but I'm removing it since it can be a cross-site leak, and blocks fenced frames since it opens a communication channel. WebKit only propagates it for `.focus()`, but not for the selection API. Note that even if the contents in the nested browsing contexts are not marked as inert, if the browsing context container is inert, they won't respond to mouse interactions, and they won't be reached by sequential navigation. Fixes whatwg#7605.
domenic
approved these changes
Feb 17, 2022
Member
domenic
left a comment
domenic
left a comment
There was a problem hiding this comment.
Thanks for walking me through the issues over in #7605. Things we should follow up on:
- Web platform tests for mouse move events
- Spec changes to make inertness be in terms of pointer-events: none
- Tests that you can tab out of the iframe as you described in #7605 (comment)
Contributor
Author
|
OK thanks. Can you review web-platform-tests/wpt#32817 ? |
Loirooriol
deleted the
stop-propagating-inertness-into-nested-browsing-contexts
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Firefox doesn't propagate it. Blink does, but I'm removing it since it
can be a cross-site leak, and blocks fenced frames since it opens a
communication channel. WebKit only propagates it for
.focus(), but notfor the selection API.
Note that even if the contents in the nested browsing contexts are not
marked as inert, if the browsing context container is inert, they won't
respond to mouse interactions, and they won't be reached by sequential
navigation.
Fixes #7605.
(See WHATWG Working Mode: Changes for more details.)
/interaction.html ( diff )