From 0ff056f8527b2c68c3bcc44fc78915bb52a457de Mon Sep 17 00:00:00 2001 From: Taylore Date: Thu, 24 Apr 2025 10:23:17 -0700 Subject: [PATCH 1/4] Create ElementInternalsType --- .github/ISSUE_TEMPLATE/ElementInternalsType | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/ElementInternalsType diff --git a/.github/ISSUE_TEMPLATE/ElementInternalsType b/.github/ISSUE_TEMPLATE/ElementInternalsType new file mode 100644 index 000000000..929c541b3 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/ElementInternalsType @@ -0,0 +1,8 @@ +--- +name: ElementInternalsType API +about: new issue +title: "[ElementInternalsType] " +labels: ElementInternalsType +assignees: anaskim + +--- From 2ea3014077c04ccacc4e20d05cb95442c1194ca2 Mon Sep 17 00:00:00 2001 From: Taylore <givenstaylore@gmail.com> Date: Thu, 24 Apr 2025 10:39:13 -0700 Subject: [PATCH 2/4] Update active explainer w ElementInternals API README.md adding ElementInternals to active explainers readme list --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index c0c38797d..2059f9806 100644 --- a/README.md +++ b/README.md @@ -89,6 +89,7 @@ we move them into the [Alumni section](#alumni-) below. | [Contextual Logging With Console Context](ContextualLoggingWithConsoleContext/explainer.md)| <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/Contextual%20Logging%20With%20Console%20Context">![GitHub issues by-label](https://img.shields.io/github/issues/MicrosoftEdge/MSEdgeExplainers/Contextual%20Logging%20With%20Console%20Context?label=issues)</a>| [New issue...](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?template=contextual-logging-with-console-context.md)| WHATWG | | [Expose resource dependency in Resource Timing](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ResourceTimingInitiatorInfo/explainer.md) | <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/Resource%20Timing%20Initiator%20Info">![GitHub issues by-label](https://img.shields.io/github/issues/MicrosoftEdge/MSEdgeExplainers/Resource%20Timing%20Initiator%20Info?label=issues)</a> | [New Issue...](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?template=resource-timing-initiator-info.md&assignees=guohuideng2024) | Web Perf | | [Allow SVG `use` to reference entire files](SVG/allow-use-to-reference-entire-files.md)| <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/SVG%20Use%20reference%20entire%20file">![GitHub issues by-label](https://img.shields.io/github/issues/MicrosoftEdge/MSEdgeExplainers/SVG%20Use%20reference%20entire%20file?label=issues)</a>| [New issue...](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?assignees=goldenboy777&labels=SVG%20Use%20reference%20entire%20file&template=allow-use-to-reference-entire-files.md&title=%5BSVG%5D+%3CTITLE+HERE%3E)| SVG | +| [Customizable Built-In Custom Elements with ElementInternals.type](ElementInternalsType/explainer.md)| <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/issues?q=is%3Aopen+label%3A%22ElementInternalsType%22+">![GitHub issues by-label]()</a>| [New issue...]()| DOM | # Brainstorming 🧠 From cfe28bd4af6a27d8c2f0ad9eb87627aa2fe52400 Mon Sep 17 00:00:00 2001 From: Taylore <givenstaylore@gmail.com> Date: Thu, 24 Apr 2025 11:17:35 -0700 Subject: [PATCH 3/4] Update ElementInternalsType explainer.md Adding a "Questions of Interest" section and explanation of how to leave feedback. Theses include questions we'd like to see discussion and debate from the community about. --- ElementInternalsType/explainer.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/ElementInternalsType/explainer.md b/ElementInternalsType/explainer.md index f96fb0e46..784444713 100644 --- a/ElementInternalsType/explainer.md +++ b/ElementInternalsType/explainer.md @@ -179,6 +179,9 @@ Both `extends` and `is` are supported in Firefox and Chromium-based browsers. Ho The `elementInternals.type` proposal addresses many of the limitations with `extends`/`is`, including allowing customized built-ins to support shadow DOM. The proposal also has support from the WHATWG and multiple browser vendors (including Safari) as noted by a WG resolution here: https://github.com/openui/open-ui/issues/1088#issuecomment-2372520455. +## Questions of Interest +If a declarative implementation is considered, how should it be done so it would align with the future creation of a declartive implementation for custom elements? + ## Stakeholder Feedback / Opposition - Chromium : Positive @@ -192,4 +195,8 @@ The `elementInternals.type` proposal addresses many of the limitations with `ext Many thanks for valuable feedback and advice from: - [Mason Freed](https://github.com/mfreed7) -- [Open UI Community Group](https://www.w3.org/community/open-ui/) \ No newline at end of file +- [Open UI Community Group](https://www.w3.org/community/open-ui/) + +## Feedback + +Please leave feedback by following the instructions on the [readme](https://github.com/MicrosoftEdge/MSEdgeExplainers/tree/main#) page to submit an issue, contribute to an existing issue, or submit a PR on the explainer document itself. From 61973de3fc363c8cf7a3c8d435d34ebdb6b54ae8 Mon Sep 17 00:00:00 2001 From: Taylore <givenstaylore@gmail.com> Date: Thu, 24 Apr 2025 11:21:28 -0700 Subject: [PATCH 4/4] Update ElementInternals explainer.md ElementInternals explainer added "Feedback" and "Questions of Interest" section --- ElementInternalsType/explainer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ElementInternalsType/explainer.md b/ElementInternalsType/explainer.md index 784444713..13fab742e 100644 --- a/ElementInternalsType/explainer.md +++ b/ElementInternalsType/explainer.md @@ -180,7 +180,7 @@ Both `extends` and `is` are supported in Firefox and Chromium-based browsers. Ho The `elementInternals.type` proposal addresses many of the limitations with `extends`/`is`, including allowing customized built-ins to support shadow DOM. The proposal also has support from the WHATWG and multiple browser vendors (including Safari) as noted by a WG resolution here: https://github.com/openui/open-ui/issues/1088#issuecomment-2372520455. ## Questions of Interest -If a declarative implementation is considered, how should it be done so it would align with the future creation of a declartive implementation for custom elements? +If a declarative implementation is considered, how should it be done so it would [align with the future creation of a declarative implementation](https://github.com/openui/open-ui/issues/1088#issuecomment-2375184147) for custom elements? ## Stakeholder Feedback / Opposition