Mason Freed

Results 546 comments of Mason Freed

> Now it's possible we can do a special "do the thing" for popover but more likely we should build it into the API. My thought was that the "auto"...

I gave this (a lot) more thought. I'm leaning toward the conclusion that really, we don't need/want an `interestaction` attribute at all. The point is that "gaining" and "losing" interest...

> Btw the intention is just to do popovers for interest, not the other actions (opening a modal dialog might be problematic for example). I guess the openable attribute might...

I'm definitely supportive of the effort to clean this up, and make WPT the source of truth for parser tests.

+1 to the OP. I've prototyped this in Chrome ([see the chromestatus](https://chromestatus.com/feature/5120638407409664) for details), and I've chosen this API: ```webidl boolean togglePopover(optional (TogglePopoverOptions or boolean) options); void showPopover(optional ShowPopoverOptions options);...

Ok, if I'm reading all of the comments correctly, it kind of sounds like rough consensus on the *shape* of https://github.com/whatwg/html/issues/10675#issuecomment-2415232403, does that sound right? > Apologies for doing this...

> One question I have, does the invoker that's passed work even if it's in a shadow root? Good question. Based on the fact that there's no way to imperatively...

> Essentially, you can set the invoker via `popover.showPopover({invoker: button})` and that does all the "normal" things that `popovertarget` already does. Plus as part of that change, both `popovertarget=foo` and...

I put up a spec PR containing the proposal detailed above: https://github.com/whatwg/html/pull/10728 As mentioned above, it also includes a solution for #10442.

> Now let's look at two specific differences: > > 1. Because of the first bullet above, I would expect `pointerout` and `pointerleave` events getting dispatched to `#filler`. Chrome and...