Skip to content
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

The querySelector method works incorrectly if it contains the href attribute with a hash value #922

Closed
AlexanderMoskovkin opened this issue Nov 8, 2016 · 2 comments
Labels
!IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Milestone

Comments

@AlexanderMoskovkin
Copy link
Contributor

AlexanderMoskovkin commented Nov 8, 2016

pages: http://todomvc.com/examples/vanillajs/ http://todomvc.com/examples/vanilla-es6
error: Uncaught TypeError: Cannot set property 'className' of null

reproduced in playground. Tested in Chrome but should be checked in other browsers

@georgiy-abbasov
Copy link
Contributor

I'm working on this

georgiy-abbasov pushed a commit to georgiy-abbasov/testcafe-hammerhead that referenced this issue Nov 9, 2016
@miherlosev miherlosev changed the title [todomvc] Js-error appears on the on the VanillaJS demo page querySelector method wrong works if it contains the href attribute with hash value Dec 1, 2016
@MarinaRukavitsyna MarinaRukavitsyna changed the title querySelector method wrong works if it contains the href attribute with hash value The querySelector method works incorrectly if it contains the href attribute with a hash value Dec 1, 2016
AndreyBelym pushed a commit to AndreyBelym/testcafe-hammerhead that referenced this issue Feb 28, 2019
* querySelector behavior fixed (closes DevExpress#922)

* Test name fixed

* Some remarks
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked Issues that were automatically locked by the Lock bot label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
!IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Projects
None yet
Development

No branches or pull requests

2 participants