Vibration API Recommendation errata #1
Merged
Conversation
This file contains 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
These non-normative changes align the Vibration API spec with the latest Page Visibility API spec by tapping into its hooks defined post-Vibration API Recommendation publication: - determine if the document is hidden - visibility states In addition, terminology is clarified as follows: - browsing context -> top-level browsing context
|
@chaals Updated as follows: anssiko@ad43bf8 |
|
where do we stand on this? what's our next step to the PER transition? |
|
I merged this PR, since no concerns were raised for the proposed changes. Please review it in context at https://w3c.github.io/vibration/ @dontcallmedom If this looks good, then I'd expect we publish a PER using this ED as the source. I still need to update the Status of This Document. Any specific text needed for PER, or is the usual diff from REC2PER fine? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These non-normative changes align the Vibration API spec with the
latest Page Visibility API spec by tapping into its hooks defined
post-Vibration API Recommendation publication:
In addition, terminology is clarified as follows:
The privacy and security considerations section was added
Link to the Simplified Chinese translation was added