-
Notifications
You must be signed in to change notification settings - Fork 120
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
Incorrect selectors for querySelectorAll #48
Comments
Thanks, a nice one. It gets included in v3.0.1 |
When will it be? |
I believe in a week, want to collect other possible issues for the release |
I really want to try puppetry. But I can't until this fix are released. |
But as I understand, you built Puppetry when testing the fix. So you can run it like "npm start". I need extra checks before releasing the last changes. |
Nope. :-) |
You can play with dev version https://we.tl/t-jyrOwDnXGu |
Oops, didn't get it. Recorder tries to suggest a passing name automatically. Optionally you can right-click on a target and specify a custom name. |
I don't want to name selectors (so for assertion I have no choice), I want to use selector itself (but without escaping of course). |
In your particular case it's so, but usually the selectors are like "div > div:nth-child(2) > div:nth-child(2) > div:nth-child(2) > div:nth-child(2)". Too long for searching in select and meaningless. You can rename targets as you wish. When editing as CSV (as a text) you can use any tools for bulk renaming. |
"div > div:nth-child(2) > div:nth-child(2) > div:nth-child(2) > div:nth-child(2)" is too fragile selectors. So in my architecture all elements have user-readable stable semantic id's. I don't want fragile selectors. So I don't want to name or rename selectors. I want selectors naming to be totally optional. |
App: https://mol.js.org/app/todomvc/
You should use
getElementById
:Or use right escaping:
The text was updated successfully, but these errors were encountered: