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

Rules for when devicechange events may fire #412

Merged
merged 1 commit into from
Oct 27, 2016
Merged

Rules for when devicechange events may fire #412

merged 1 commit into from
Oct 27, 2016

Conversation

ShijunS
Copy link
Contributor

@ShijunS ShijunS commented Oct 21, 2016

This is for issue #402, includes all changes in PR #407. I'll close #407 separately.

This includes all changes in PR #407.  I'll close #407 separately.
@ShijunS ShijunS mentioned this pull request Oct 21, 2016
@alvestrand alvestrand changed the title resubmit to resolve conflicts in PR #407 Rules for when devicechange events may fire Oct 27, 2016
@alvestrand
Copy link
Contributor

This resolution says that the UA MUST fire an event at the current browsing context, but doesn't say explicitly what happens with other browsing contexts. Is that intended as an affordance to let UAs do what they want to do (MAY fire), or is it intended to say that events MUST NOT be fired on contexts that don't satisfy the criteria?

Editorial: I don't see language saying what happens when a device is removed. Is it unchanged, or was it missing before too?

@alvestrand
Copy link
Contributor

@guidou can you comment?

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.

2 participants