Jumpiness from Twitter trying to reload trends widget

[dhasial]

This is definitely an improvement over the current state of things, though there is still definitely some strange jumpy artefacts from Twitter repeatedly trying to force the widget to load in-between other tweets.

[lucaswerkmeister]

Hm, I didn’t realize how bad the jumpiness was in that use case. (I use another app, Cawbird, for reading the timeline, and Twitter Web mainly for notifications and DMs.)

I’m not sure how to solve it at the moment, though. Using CSS instead of JS would be more immediate, but as far as I can tell, the top-level trends element doesn’t have any classes that other elements don’t have, even if we assume that these classes are stable:

Once Firefox has proper :has() support, it might be possible to translate the current JS logic into CSS, I’ll have to look into that later. (Very recent versions have experimental support if you enable layout.css.has-selector.enabled, but it’s so incomplete that it’s not usable yet, I think.)