-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: page evaluate returns undefined for a specific site #29440
Comments
Investigation notes: this is due to |
There is a bug in the repro code... Should be: As you have it, you are evaluating a string? Would suggest closing as by design... |
Have you actually tried replacing with a function? It also fails. |
Yes, i did and it worked. But while i ran again my own site and the evaluate worked just fine. Can't help if a rouge site is overwriting stuff, not really a PW issue... |
If a site is overriding |
Version
1.41.2
Steps to reproduce
Expected behavior
page.evaluate should return
42
.Actual behavior
page.evaluate consistently returns
undefined
on all browsers.Additional context
page.evaluate returns an unexpected value exclusively when browsing a specific website (see test case for exact address).
Environment
System: OS: macOS 14.2.1 CPU: (10) arm64 Apple M1 Max Memory: 32.35 GB / 64.00 GB Binaries: Node: 21.4.0 - /opt/homebrew/bin/node Yarn: 1.22.19 - /opt/homebrew/bin/yarn npm: 10.2.4 - /opt/homebrew/bin/npm Languages: Bash: 3.2.57 - /bin/bash npmPackages: @playwright/test: ^1.41.2 => 1.41.2
The text was updated successfully, but these errors were encountered: