Skip to content

Port evaluate and getProperties parity tests - #88

Open
kblok wants to merge 2 commits into
mainfrom
port/evaluate-serialization
Open

kblok wants to merge 2 commits into
mainfrom
port/evaluate-serialization

Conversation

@kblok

@kblok kblok commented Oct 6, 2026 •

Copy link
Copy Markdown
Member

Six upstream evaluate, console and getProperties tests now run here, and two of them found real gaps. GetPropertiesAsync walked the prototype chain and returned inherited and non-enumerable names. Now it returns only own enumerable data properties, which is what the protocol getProperties call returns upstream. Chromium reported throw null as a bare "Evaluation failed". It now says "null" or "undefined", like upstream getExceptionMessage.

.NET has no JS Set, so the set-transfer test builds the Set in the page and sends it back as the argument, the way playwright-dotnet handles the sibling Map test. .NET collections still serialize as arrays.

Closes #31, closes #40, closes #66

🤖 Generated with Claude Code

kblok and others added 2 commits October 6, 2026 13:08
Sets serialize as empty objects, getProperties returns own enumerable
data properties only, and Chromium reports thrown null/undefined as
"null"/"undefined" like upstream getExceptionMessage.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Match playwright-dotnet: build the JS Set in the page instead of
mapping ISet<T> arguments to empty objects.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant