Click events on svg element generates: CypressError: Timed out retrying: Illegal invocation
See original GitHub issueCurrent behavior:
We have a click assertion:
cy.get('[data-role="rater-button"]')
.first()
.click();
instead of it clicking and continuing, we get this error: CypressError: Timed out retrying: Illegal invocation
Desired behavior:
It should click and advance.
Steps to reproduce:
Create an svg object, select it and click it.
Versions
Cypess 3.0.3 Mac OS X (10.12.6)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:15
- Comments:30 (12 by maintainers)
Top Results From Across the Web
Timed out retrying: cy.click() failed because this element is ...
I faced same problem but you can solve it by cy.get('.mySelector').should('be.visible').click({force:true});.
Read more >Changelog - Cypress Documentation
Cypress now throws an error if any Cypress commands are invoked from inside ... Fixed a regression where absolute elements were not properly...
Read more >Tweets with replies by Brian Mann (@be_mann) / Twitter
Click events on svg element generates: CypressError: Timed out retrying: Illegal invocation · Issue... Current behavior: We have a click assertion: ...
Read more >fix this problem, or use {force: true} to disable error checking.
You could write a custom command for click called forceClick. Cypress.Commands.add('forceClick' ...
Read more >cypress: Versions - Openbase
Fixed an issue with cy.root() to respect the timeout option passed to the ... with .type() where click events could be fired on...
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 FreeTop 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
Top GitHub Comments
@0102qa we’ve already fixed the bug and it will go out in the next release
Yup this was an area that we completely rewrote and it’s a simple fix.