You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The show popover steps unconditionally1 run "the topmost popover ancestor algorithm given element" which then asserts "newPopoverOrTopLayerElement's popover attribute is not in the no popover state or the manual state".
There doesn't appear to be anything preventing the topmost popover ancestor algorithm from being called on a manual popover. Have I missed something obvious?
The results of that algorithm are only used in the step 17 conditional block where that assertion would always succeed, so it seems like a fix would be to move the calls to there.
I agree - those two calls to "topmost popover ancestor" should likely be guarded by "If originalType is auto or hint, then:...". The autoAncestor and hintAncestor values are only ever used in that case anyway.
What is the issue with the HTML Standard?
The show popover steps unconditionally1 run "the topmost popover ancestor algorithm given element" which then asserts "newPopoverOrTopLayerElement's popover attribute is not in the no popover state or the manual state".
There doesn't appear to be anything preventing the topmost popover ancestor algorithm from being called on a manual popover. Have I missed something obvious?
The results of that algorithm are only used in the step 17 conditional block where that assertion would always succeed, so it seems like a fix would be to move the calls to there.
Footnotes
Except for invalid popovers. ↩
The text was updated successfully, but these errors were encountered: