@davidak@chaos.social Unsure about the name, but it's generally caused by ill-informed hover rules that physically reposition hovered elements, leading to a loop of "hovering" -> "no longer hovering" -> "hovering" -> etc.

Can be prevented by ensuring that the hover state bounding box is always a superset of the normal state bounding box, ie. there are no points on the screen where your cursor 'hits' the bounding box in non-hover state but *doesn't* hit it in hover state.

In cases where a hover effect *must* reposition elements (usually a bad idea for UX reasons), this is often achieved by some combination of padding, background color trickery, and/or a wrapper element that the hover state and interaction handlers are actually defined on (instead of the element itself) - the objective being to 'invisibly' expand that bounding box in the hover state, so that it fully encompasses the non-hover bounding box.