You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@pearofducks Thanks for the repro. Yes, happy-dom has several issues, I would not be surprised if display: none; is one of them (as you can see here, we ware not doing anything extraordinary).
The current test suite of VTU uses jsdom and is failing when switching to happy-dom, mainly because of issues with happy-dom itself.
We have an issue tracking the possibility of running the test suite with both jsdom and happy-dom , so I'm closing this one in favor of #513
If you are interested in helping us to support happy-dom, you can try to run VTU test suite with happy-dom and investigate if the failures are caused:
by VTU, and in that case, we can try to fix it
or by happy-dom itself, in which case we can't do a lot, except by opening an issue on happy-dom repo
I'll look into that! If someone else finds this in the future a mitigation is to use attachTo to ensure the DOM element is actually placed on the document.
Describe the bug
isVisible
doesn't detect hidden elements ifhappy-dom
is used as the test environment.To Reproduce
https://github.com/pearofducks/vue-test-utils-reproduction
To counter-reproduce the
test.environment
field can be changed tojsdom
invitest.config.js
.Expected behavior
The test should pass, because the root element is hidden with
display: none
.Related information:
Additional context
The text was updated successfully, but these errors were encountered: