Jake ArchibaldFolks who are interested in popover=hint: have a play with https://random-stuff.jakearchibald.com/popover-hint/ and tell me anything that doesn't make sense. Or watch this:
vrugtehagel@jaffathecake it seems to work differently across browsers right now, but even just the behavior in the video seems inconsistent. Intuitively, the stack level for content should not affect the behavior for popovers. That is to say, if I were to throw all those buttons and popovers from the video within one giant encapsulating popover, it feels like it should do the same thing. I struggle to see a compelling argument for the contrary.
@vrugtehagel ohhh, which cross-browser differences have you seen? Although, differences in Safari don't count - they don't support popover=hint yet, so differences there are expected.
@jaffathecake scratch that then, I was on Firefox 148 (oops) and no bells started to ring because it _sort of_ worked. Now I see it the same as in Chrome, but nevertheless I'm not a huge fan of the behavior. I will also say that I find it unintuitive that the other popovers will close if the timed one does; even the hovered ones close while still being hovered (and it seems you're only calling `hidePopover()` on the timed one).
Mayank@jaffathecake why does opening the 1.3 hint popover close the 1.2 auto popover but opening the 4 hint popover not close the 1.3 hint popover? i would expect the opposite behavior.
@mayank yeah… it's not something I can make sense of either.