Labels |
Added:
No Code Attached Yet
|
err :TypeError: The following error originated from your application code, not from Cypress.
> Cannot read properties of undefined (reading 'element')
When Cypress detects uncaught errors originating from your application it will automatically fail the current test.
This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.
index.js:7 runnable :[object Object]
choices.min.js?9.1.0:2 Uncaught TypeError: Cannot read properties of undefined (reading 'element')
at e._removeEventListeners (choices.min.js?9.1.0:2:21241)
at e.destroy (choices.min.js?9.1.0:2:6770)
at HTMLElement.disconnectedCallback (joomla-field-fancy-select.min.js?5f1507ec943a2bdde346f3783754e2c0:1:4145)
e
@carlitorweb happy to see its not just me
They look different, one is in choices and one in the toolbar script.
Let me check Category.cy
run npm ci first, just to be sure no old assets are loaded
Labels |
Added:
bug
|
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2024-07-23 18:31:00 |
Closed_By | ⇒ | brianteeman |
Might as well close this one
I never get such an error when I run the tests locally. Is there something printed to the browser console where we can see in which file and on which line the error happens?