Hi Lea, No TAG review has been requested yet. "Pending" is just the default value (which might also be confusing though...)
On Fri, Aug 26, 2022 at 3:19 AM Lea Verou <leave...@gmail.com> wrote: > Hi there, > I see it says "Pending" for the TAG review, but I cannot find any TAG > review request in > https://github.com/w3ctag/design-reviews/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc > Could you please point me to it? > Thanks! > > On Thursday, August 25, 2022 at 1:06:33 AM UTC+3 xiaoc...@chromium.org > wrote: > >> Contact emailsxiaoc...@chromium.org >> >> Explainer >> https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md#overview >> >> Specification >> https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md >> >> Summary >> >> This feature allows for multiple custom element definitions for a single >> tag name to exist within a page to prevent custom element name conflicts >> when a web app uses libraries from multiple sources. This is achieved by >> allowing user code to create multiple custom element registries and >> associate them with shadow roots that function as scopes for element >> creation and custom element definitions. >> >> >> Blink componentBlink>HTML>CustomElements >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EHTML%3ECustomElements> >> >> Motivation >> >> It's quite common for web applications to contain libraries from multiple >> sources, whether from different teams, vendors, package managers, etc. >> These libraries must currently contend for the global shared resource that >> is the CustomElementRegistry. If more than one library (or more than one >> instance of a library) tries to define the same tag name, the application >> will fail. This feature solves the problem by using ShadowRoots, which >> already function as encapsulation boundaries, to also function as scopes >> for custom element definitions. >> >> >> Initial public proposal >> https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md >> >> TAG review >> >> TAG review statusPending >> >> Risks >> >> >> Interoperability and Compatibility >> >> >> >> *Gecko*: No signal >> >> *WebKit*: No signal >> >> *Web developers*: No signals >> >> *Other signals*: >> >> WebView application risks >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> >> >> >> Debuggability >> >> >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >> ?No >> >> Flag name >> >> Requires code in //chrome?False >> >> Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1304439 >> >> Estimated milestones >> >> No milestones specified >> >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5090435261792256 >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com/>. >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFqEGhbLNaN9zvp5msuHm-BhG0Gs1LOTJUPMCG1ELyvJr_cc8w%40mail.gmail.com.
