[Bug]: element.tagName.toUpperCase is not a function #30616
Assignees
Labels
Comments
|
@juvarabrera Thank you for the issue. The problem is most likely during the search for the button, so the element that triggers Unfortunately, without a repro we won't be able to help, because we need to see the markup that triggers this unexpected behavior. If you could provide a repro, perhaps removing parts of the page while the issue still reproduces, that would be great! |
|
This is what |
|
@juvarabrera @dgozman i'm facing the same issue "javascript error: a.tagName.toUpperCase is not a function", is there any solution we have? |
|
@juvarabrera Thank you for the snippet, I can repro. Investigation notes:
|
yury-s
pushed a commit
that referenced
this issue
May 2, 2024
dgozman
added a commit
to dgozman/playwright
that referenced
this issue
May 2, 2024
dgozman
added a commit
that referenced
this issue
May 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
1.40.1
Steps to reproduce
We have a big web application and we've been using Playwright for almost all pages. But there is one particular page that's showing this error in Playwright.
I have this snippet that clicks this button
The button is visible in plain sight.
Expected behavior
I just expect that the button is clicked. I've been using the
.click()function to click thousands of buttons but any buttons in this particular page is not working. I'm not a dev that's working on this particular page so I'm not sure what's differentActual behavior
It does not wait for the timeout to finish (10 seconds). It just shows the error right away.
Additional context
The Save button.
All buttons are like this in other pages but it works on other pages.
I unfortunately cannot disclose the web application for you to try but please let me know what information you need to debug this.
Environment
System: OS: Windows 11 10.0.22631 CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz Memory: 2.51 GB / 15.70 GB Binaries: Node: 20.11.0 - C:\Program Files\nodejs\node.EXE Yarn: 4.1.0 - C:\Program Files\nodejs\yarn.CMD npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD pnpm: 9.0.5 - C:\Program Files\nodejs\pnpm.CMD IDEs: VSCode: 1.88.1 - C:\Users\Juvar\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD npmPackages: @playwright/test: ^1.40.1 => 1.42.1The text was updated successfully, but these errors were encountered: