Compare Document.hidden with a boolean #419
Merged
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
The spec confused the `hidden` attribute with the `visibilityState` attribute. The latter is a string that can take the value `"hidden"`. The former is a boolean that is true when `visibilityState` equals `"hidden"`. This update fixes that and drops the now useless references to the Page Visibility spec (now integrated in HTML).
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.
The spec confused the
hiddenattribute with thevisibilityStateattribute. The latter is a string that can take the value"hidden". The former is a boolean that is true whenvisibilityStateequals"hidden".This update fixes that and drops the now useless reference to the Page Visibility spec (now integrated in HTML).
(triggered by @kainino0x's comment in #412 (comment))
Preview | Diff