Mason Freed

> I'm playing with Declarative shadow dom and found that, if a stylesheet is loaded inside a declarative shadow DOM template, the rendering is blocked. Safari (that also implement declarative...

Just to clarify, if we resolve this issue the way you're requesting, this will still be allowed, right? ```html ... ... ```

> I agree that a change shouldn’t fire until the user has purposefully chosen an option, but with current select elements the displayed option in the triggering element does change....

> > I agree that a change shouldn’t fire until the user has purposefully chosen an option, but with current select elements the displayed option in the triggering element does...

> [#305 (comment)](https://github.com/WebKit/standards-positions/issues/305#issuecomment-2231000262) onward is still very relevant unfortunately. Thanks for the quick response here. Please help me understand the specifics of the concern, though. In particular, the critical part...

> Not really, see [whatwg/html#11058](https://github.com/whatwg/html/issues/11058). Thanks - I hadn't noticed that comment. I just replied there. > (And to be clear, there might be other concerns here too.) Ok, makes...

@annevk, thanks for the detailed reply! > Our problem with the proposal is that it primarily solves the problem for desktop users using a mouse. This goes against the media...

Some random thoughts on a few things: 1. The Anchor Positioning code snippet could be a bit bigger. At a minimum, perhaps instead of `anchor-name`, use `position-area` as the one...

I'm tentatively removing Agenda+ - feel free to put it back if you'd like to discuss this again.

> If the option can be updated without the content of the `` updating along with it without JS, this has the likelihood of leading to broken forms. I don't...