Skip to content

Tayloregivens element internals #1042

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions .github/ISSUE_TEMPLATE/ElementInternalsType
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
name: ElementInternalsType API
about: new issue
title: "[ElementInternalsType] <TITLE HERE>"
labels: ElementInternalsType
assignees: anaskim

---
9 changes: 8 additions & 1 deletion ElementInternalsType/explainer.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 declarative implementation](https://github.com/openui/open-ui/issues/1088#issuecomment-2375184147) for custom elements?

## Stakeholder Feedback / Opposition

- Chromium : Positive
Expand All @@ -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/)
- [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.
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,8 +89,10 @@ 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 |
| [Gamepad Event-Driven Input API](GamepadEventDrivenInputAPI/explainer.md) | <a href="https://github.com/MicrosoftEdge/MSEdgeExplainers/labels/Gamepad%20Event-Driven%20Input%20API">![GitHub issues by-label](https://img.shields.io/github/issues/MicrosoftEdge/MSEdgeExplainers/Gamepad%20Event-Driven%20Input%20API?label=issues)</a> | [New issue...](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?assignees=snehagarwal1&labels=Gamepad%20Event-Driven%20Input%20API&template=gamepad-event-driven-input-api.md&title=%5BGamepad%20Event-Driven%20Input%20API%5D%20%3CTITLE%20HERE%3E) | Gamepad |


# Brainstorming 🧠

These are proposals that are still really early in their lifecycle. We might just be thinking about the problems, starting to get rough ideas of what solutions might look like, or just want to throw an idea out to the world to see if there's more people with similar problems. Once we get a handle on the possible solutions and directions we'll move these to the "Active Explainers" section above.
Expand Down