fix: get ownerDocument before calling element.evaluate(...) #1826
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
refactor: extract getOwnerDocument helper function to follow DRY principle
✅ Deploy Preview for content-scope-scripts ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Temporary Branch UpdateThe temporary branch has been updated with the latest changes. Below are the details:
Please use the above install command to update to the latest version. |
[Beta] Generated file diffTime updated: Tue, 15 Jul 2025 18:36:02 GMT AndroidFile has changed IntegrationFile has changed WindowsFile has changed AppleFile has changed |
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.
Context
in data-broker-protection debugger when using
safeQuerySelectorXPath, a DOMException was thrown with the message:This occurred because nodes created in one document (e.g., from an iframe) cannot be used in another document context.
Solution
Added a check to ensure that the node’s ownerDocument matches the current document before proceeding with operations in safeQuerySelectorXPath. This prevents cross-document node usage and avoids the DOMException.