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

Remove focused requirement #303

Merged
merged 1 commit into from Sep 26, 2019
Merged

Conversation

beaufortfrancois
Copy link
Collaborator

@beaufortfrancois beaufortfrancois commented Aug 21, 2019

As raised in https://bugs.chromium.org/p/chromium/issues/detail?id=996250, I think* we should remove the focused requirement for Document as it causes some confusion.

In the example for instance, an iframe with a focused "input" element causes WebNFC operations to be suspended.


Preview | Diff

@zolkis
Copy link
Contributor

zolkis commented Aug 21, 2019

What we intend to mean is that the page should be the one the user is interacting with. I don't know what is the best way nowadays to express that. Visible is not enough IMHO.

@kenchris
Copy link
Contributor

Maybe @domenic has input

@kenchris
Copy link
Contributor

We agreed at TPAC that we should remove the focused requirement and rely on visibility change instead. Want to rebase @beaufortfrancois

@anssiko @riju can you share the notes from that discussion?

@beaufortfrancois
Copy link
Collaborator Author

@kenchris Does it need rebase?
image

@kenchris
Copy link
Contributor

Maybe not... let me merge, but maybe you should check whether our visibility spec text covers the requirements

@kenchris kenchris merged commit 748e682 into w3c:gh-pages Sep 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants