Implementation bug for popover-inside-invoker fix
Categories
(Core :: DOM: Core & HTML, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox143 | --- | fixed |
People
(Reporter: masonf, Assigned: keithamus)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36
Steps to reproduce:
This is an implementation bug for this spec PR:
https://github.com/whatwg/html/pull/10770
It fixes a corner case issue with the behavior of a popover nested inside the invoker for that popover.
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Core & HTML' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•1 year ago
|
| Assignee | ||
Comment 2•4 months ago
|
||
Given a structure like:
<button popovertarget=foo>Activate
<div popover id=foo>Clicking me shouldn't close me</div>
</button>
With the popover open, clicking the popover will propagate a click
upward to the button, which will close the button. This change ensures
that the original target is checked, and if it is a
ShadowIncludingDescendantOf the button then the popover behaviour is not
invoked.
Updated•4 months ago
|
Comment 5•4 months ago
|
||
| bugherder | ||
Updated•3 months ago
|
Description
•