Skip to content
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

[css-nav-1] Keeping related feature policies consistent accross the web platform. #3656

Open
frivoal opened this issue Feb 19, 2019 · 1 comment
Assignees

Comments

@frivoal
Copy link
Collaborator

frivoal commented Feb 19, 2019

This issue is a reminder to keep an eye on w3c/webappsec-permissions-policy#273, when a decision is reached there to (probably) synchronize https://drafts.csswg.org/css-nav-1/#policy-feature with it.

That issue in the web-app-sec WG is dealing with a different facet of the same problem, so we should try and keep things consistent.

@frivoal frivoal self-assigned this Feb 19, 2019
@jihyerish
Copy link
Contributor

jihyerish commented May 30, 2019

focus-without-user-activation is a new feature policy that can be used to block programmatic focus changes. This feature affects element/window.focus() and 'autofocus'.

In spatial navigation, we have window.navigate() which can programmatically move the focus.
Also, navbeforefocus and navnotarget are related to programmatic focus changes.
So, I think those also need to be disabled by focus-without-user-activation.

Furthermore, preventing keydown event when it occurs one of arrow keys are pressed can also cause focus trapping.
We also need to consider this case.

Test page: https://wicg.github.io/spatial-navigation/tests/internal/hostile_iframe_test.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants