Some DOM elements appear on
hover because in CSS they’re targeted with a
:hover entry. In those cases, you can use the attribute modifier in Chrome to synthesize
:hover, which lets you inspect the element in its hovered state without having to physically modify the document.
In many other cases though, DOM elements appear on
hover via a JS
onmouseover event or similar, which hoverIntent (or a similar in-house solution) picks up and programmatically applies a CSS class or series of classes. In this scenario, freezing the DOM to a state where you can access the modal / popup / tooltip / whatever is harder. That’s where this Stack Overflow solution comes in. I wish I’d known about this years ago.