Why does popover hide when the popover attribute changed about html HOT 4 CLOSED

@josepharhar will be able to answer this succinctly.

from html.

I think it would introduce complexity and unexpected states to allow switching between popover types without closing the popover. For example, we currently only allow multiple popover=auto popovers to be open if they are associated via a relationship, such as if one is a dom ancestor of another. If we allowed an unrelated popover to switch from popover=manual to popover=auto, should we close all other popover=auto popovers? If we don't then other algorithms would encounter an invalid state, and if we do then we have to add a bunch of partially duplicated code from the hide popover algorithm.

I have a case: there's a global tooltip (implements with popover also) in popover (call it "X" alias).
When the X popover shown, then shows the global tooltip, the X popover auto closed.

Why does your popover need to change states after opening? Why can't it just have popover=manual before it opens?

from html.

@josepharhar Thanks for your reply.
In my case, the popover and tooltip both needs light dismiss, so it setted as auto.
But when the tooltip shows, don't want to hide it.

So changed it's attribute from auto to manual when tooltip shows, and change back after closed.

Maybe the only case is tooltip, a global one without ancestor relationship to other elements.

from html.

Ah I see your use case, it would be perfectly handled by the proposed popover=hint value:
#9776
#9778
I'm going to close this issue in favor of #9776
Please comment there if that proposal doesn't fit your use case in any way, but I believe it will.

from html.