Add Document member support notes for Chrome #25619
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
This includes some fixes where current data was wrong: - `hasFocus` was only added in Chrome 34 - `close`, `open`, `writeln` were already fixed in Chrome 45. - `dir`, `embeds`, `plugins` were already fixed in Chrome 36.
github-actions
bot
added
data:api
Elchi3
approved these changes
Jan 10, 2025
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.
Summary
For every
Documentmember that, in some Chrome versions, is only exposed toHTMLDocument(and not also toSVGDocumentandXMLDocument), ensures that there is a corresponding note.Test results and supporting details
Source: https://github.com/caugner/document-members/blob/main/SUMMARY.md#chrome
Related issues
Part of #10682.