Should there be a feature to disallow DOM subtrees from find-in-page matching?

[chrishtr]

Example:

https://twitter.com/omar_degan/status/1135263048351043586

Click on the image. There will be another faded image behind it that is not really "visible" to the user yet still draws pixels, and therefore the UX should not match it in find-in-page.

@bgirard

[chrishtr]

I guess sites could abuse this feature in a user-hostile way.

However, user-select already exists for the selection feature, and that one seems a stronger case for abuse from sites than find-in-page, since it makes it hard to cut-and-paste "copyrighted" or otherwise restricted text.

https://drafts.csswg.org/css-ui-4/#propdef-user-select

[vmpstr]

I think that's a reasonable feature to have. Is there a viable workaround here? I guess what I'm wondering if this necessitates a new feature or whether we can do some other techniques to do this... The reason I'm wondering is that I think this case might be frequently overlooked by developers, and so not necessarily widely requested.