I use this technique of DOM filtering with uBlock to defeat "engagement" features and improve site experience a lot. My problem comes with pages where the HTML

I use this technique of DOM filtering with uBlock to defeat "engagement" features and improve site experience a lot. My problem comes with pages where the HTML element classes are not semantic, but compiled by a tool like tailwind, e.g. <div class="erslblw0"> ... </div> For example, if you go to nytimes.com and use uBlock's 'zapper' to select an element to hide, you'll get a query selector like this: .erslblw0.css-163q563 > .css-13dv6mc These are dependent on the build, and can change day to day. Has any one come up with a solution for this situation, beyond painstakingly manually constructing positional CSS selectors (nth-of-type, etc..)?