Interactions between inert and hidden="until-found" and beforematch events

[romainmenke]

What is the issue with the HTML Standard?

Chrome is the only browser supporting all three features (as far as I know).

And up until Chrome 123 it was possible to set an element to inert, visually hide it with hidden="until-found".
We could then reveal it and make it non-inert through a beforematch event listener.

This was really handy to make accordions as the closed panels should be inert but we still want users to be able to search for text in a page and that the panel is opened and scrolled to when there is a match.

In Chrome 124 this stopped working.

When reading through the spec text for inert it doesn't specifically say that an element should not be findable through search in a page.

So I am not sure if this is a browser bug, or something that never should have worked in the first place and was actually fixed in Chrome 124.

Happy to file browser bugs if this is an issue in Chrome, but wanted to know the actual expected behavior first.