"Expect axe._selectorData to be set up" console errors
See original GitHub issueI’m getting the following error in the browser console when running aXe in my React app:
I saw this was reported on the react-axe repository, but it appears the root issue is in axe-core. I saw that the selector code had minor changes in 3.4.0 released today, but they did not fix the issue for me.
I saw similar, possibly related issues here (#1041 and #1084), but I wasn’t sure if they were true duplicates. If so, I’ll throw my +1 into those tickets for a fix.
Versions and environment
axe-core@3.4.0
(also tested with 3.3.2)react-axe@3.3.0
react@16.10.2
- Node 12
- Windows 10
- Chrome
Thanks!
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
axe-core/axe.js - chromium/src/third_party - Git at Google
console.log('Could not create a template function: ' + str); ... throw Error('Expected symbol but end of file reached.'); ... _selectorData to be set...
Read more >Console Errors - Support Axeptio
While using Axeptio, you may encounter some errors in your browser console. To comfort you, we have listed here the most common ones: ......
Read more >Jest: mocking console.error - tests fails - Stack Overflow
Using this simplified example component and test, I'd expect the two tests to behave as such: The first test with 0/2 required props...
Read more >Debugging in JavaScript: Reading Console Errors
When we open the console, any glaring errors will show up in red with an X to the left of the message. Meanwhile,...
Read more >The Horror of Console Error Screens | FonderAxe - YouTube
404 error : Description not found#FonderAxe03 #halloween ... The Horror of Console Error Screens | FonderAxe. 3.3K views 1 year ago.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is very likely because axe is started a second time before it completed the first. Axe-core can’t have multiple runs going at the same time. @straker and I discussed last week if we could put together some kind of queue, so that axe-core doesn’t start a run while another is still going. I think that’s the best way to solve this.
Apart from release doc, there is no specific axe related documentation to verify, so closing this ticket