> This PR is still getting pretty active review comments. At least some of
them seem like they'll impact the behavior. Do you think it would be
reasonable to wait for the PR to settle before approving? I don't think we
necessarily need to wait for formal approval or merging, but it seems like
right
LGTM3
On Fri, Oct 11, 2024 at 3:12 PM Chris Harrelson
wrote:
> LGTM2
>
> I think it makes sense at this point to start finching/turning on this API
> freely on the stable channel, in order to inform the final spec
> language and landed PR. This is also the main risk factor identified in the
> Mo
LGTM2
I think it makes sense at this point to start finching/turning on this API
freely on the stable channel, in order to inform the final spec
language and landed PR. This is also the main risk factor identified in the
Mozilla standards position request.
I think this is inherently a chicken-and
I agree with Domenic about TAG risk; just flagging this as part of the
larger package is great.
Will the rollout of this change be Finch controlled? Do you expect the
launch to happen over a single release? If you do a partial rollout for
compat reasons and it goes sideways, please let us know.
On Fri, Oct 11, 2024 at 5:33 AM Joey Arhar wrote:
> Contact emailsjar...@chromium.org
>
> Explainerhttps://open-ui.org/components/customizableselect
>
> Specificationhttps://github.com/whatwg/html/pull/10557
>
This PR is still getting pretty active review comments. At least some of
them seem lik
Contact emailsjar...@chromium.org
Explainerhttps://open-ui.org/components/customizableselect
Specificationhttps://github.com/whatwg/html/pull/10557
Summary
This change makes the HTML parser allow additional tags in besides
, , and . This change is in support of the
customizable feature but is
