Dan Clark

I'm inclined to agree with this. I think we'll need to do some experimenting to see how robust the user-slotted parts are to changes in the control HTML structure. If...

cc @tabatkins @rakina @mfreed7 If I wrote a PR to update this spec to match the current Chromium implementation, would it be accepted? Or was the plan to wait until...

I'm finally getting to this with https://github.com/WICG/construct-stylesheets/pull/137 and https://github.com/WICG/construct-stylesheets/pull/138. One change from the plan I discussed [here](https://github.com/WICG/construct-stylesheets/issues/123#issuecomment-721968587) is that for now I think CSS modules should still reference the steps...

Thanks for pointing this out! For custom highlights at least, the original intention of the custom highlight [#default-styles](https://drafts.csswg.org/css-highlight-api-1/#default-styles) was indeed for an unstyled ::highlight to yield no visible change in...

Ah, I'd missed that #6665 was also addressing this for custom highlights. It looks great to me!

> (just like module scripts have stricter MIME type restriction than classic scripts) Is anyone familiar with the reasoning behind that decision? That could help inform our thinking here. In...

I'm thinking that in this case the benefit of allowing potential JSON-like types like `image/foobar+json` to be loaded as JSON modules outweighs any benefit of narrowing the JSON MIME-type set....

Thanks for raising this, I agree that it could be useful to have `` handle this by default. That said it's not clear how the control could do this in...

I expect the specification to cover this use case. The `` should find its options using a "flat tree" walk, which is basically the view that you get after all...

Markdown ate the elements in the above copy/paste from the minutes; here's the resolution with those included: > Resolved: ``'s shadow DOM has a `` around the button's default arrow...