Repository navigation
Conversation
Add page.content({ includeShadow }) as ContentAsync(PageContentOptions),
serializing open shadow roots as declarative shadow DOM like upstream
injectedScript.documentContent. Port the COOP/COEP history-state goto
tests. Listener-leak, __testHookBeforeAdoptNode and toImpl utility-world
setContent tests get Node-only ignored twins.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Upstream added
page.content({ includeShadow: true }), which serializes open shadow roots as declarative shadow DOM.Microsoft.Playwrightdoes not expose it yet, so it lands here aspage.ContentAsync(new PageContentOptions { IncludeShadow = true }). All three engines use the upstreamdocumentContentscript. The COOP/COEP history-state goto tests needed no library change and now pass on Chromium and WebKit.Seven upstream titles only test Node internals, so they get ignored twins with the reason written out. The three listener-leak tests watch for Node's
MaxListenersExceededWarning. .NET events have no listener cap and no such warning. The two wait-for-selector tests drive__testHookBeforeAdoptNode. Local waitForSelector polls the main world and has no adoption step to hook into. The two setContent timeout tests usetoImplto tamper with the server utility world. Local setContent has no persistent utility world and no console.debug tag.Closes #19, closes #44, closes #32
🤖 Generated with Claude Code