Ernesto García

> The class ant-popover-hidden has display: none. That class is applied to an ancestor. Are you certain the CSS is loaded and attached to the document in the context of...

> Anyway I don't like basing the test on external class. I get your point, but OTOH, you'd base your tests on needed to load a css resource over the...

Hi, thanks for taking the time to report this. I am having no luck reproducing it though. I just added the following test to the test module for `toHaveStyle` and...

As mentioned before, a minimal repository where this can be reproduced would go a long way towards figuring this out.

- Does this happen only with the `toBeChecked` matcher? Or with any matcher? - I strongly recommend that you provide a sample repo where the problem occurs. Otherwise, without access...

@markusv I may be able to take care of this in a week or two. But maybe you could take a shot at it? You are welcome to make a...

Indeed, #276 was there for a reason, and unfortunately, we had not been covering in a test the support for these custom properties, which would've flagged this when it was...

Option (1) seems reasonable enough without the extra overhead of the case converter.

BTW @thomlom in the mean time, while this is resolved, you need not have a fork. You can fix the version in your package.json to the one prior to the...

:tada: This issue has been resolved in version 5.11.3 :tada: The release is available on: - `npm package (@latest dist-tag)` - [GitHub release](https://github.com/testing-library/jest-dom/releases/tag/v5.11.3) Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket: