Ernesto García

@MarcoLeko you may be experiencing an additional issue where styles from a stylesheet are not loaded automatically in jest/jsdom test env where you load and test the component in isolation....

Thanks for letting us know @tatinacher. I'll close this issue now.

Oh ok, sorry. The signal here got lost between all the noise of styled components and the concern about stylesheets being loaded or not. Indeed, it is a mistake that...

I've got a PR ready that fixes this issue: https://github.com/testing-library/jest-dom/pull/428

BTW, @codewaseem, your example is not related to this issue. It does not involve the `visibility` CSS property at all. I believe your example is suffering from the issue that...

If it's something that you can reproduce regardless of it being related to the `visibility` CSS property, then open a new issue, please. If it works in codesandbox but not...

@uzikilon can you expand a little bit more on how/when/where this bug happens? I'm checking the [`css` lib documentation](https://github.com/reworkcss/css#readme) and I see that the recommended way to import it is...

Oh thanks, that clarifies it. Could you raise the issue in that library without closing this one, and you can reference this issue over there? I'd rather not introduce these...

> because sporadically `getRootNode` returns the React node that got matched itself rather than the `Document` Hmmm, this seems to be the key of the issue. However, we do not...

FWIW, I was planning to take some time next week to gather this and at least one other PR that are breaking changes, and make a single new major release...