Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Custom Builtins #234

Closed
josepharhar opened this issue Oct 20, 2022 · 6 comments
Closed

Custom Builtins #234

josepharhar opened this issue Oct 20, 2022 · 6 comments
Labels
focus-area-proposal Focus Area Proposal

Comments

@josepharhar
Copy link

josepharhar commented Oct 20, 2022 •
edited
Loading

This was split from #181

I had a hard time finding a good description and rationale for this feature, but it is in the HTML spec and has WPTs.

Tests

Spec

https://html.spec.whatwg.org/multipage/custom-elements.html#customized-built-in-element
@josepharhar josepharhar mentioned this issue Oct 20, 2022
Closed
@domenic
Copy link
Member

domenic commented Oct 21, 2022

I had a hard time finding a good description and rationale for this feature

I think https://html.spec.whatwg.org/multipage/custom-elements.html#custom-elements-customized-builtin-example and the following section serve that purpose.

@gsnedders gsnedders added the focus-area-proposal Focus Area Proposal label Oct 21, 2022
@gsnedders
Copy link
Member

gsnedders commented Oct 21, 2022 •
edited
Loading

This is another case where our existing scoring absolutely falls apart due to only having two tests, and with those two tests have very different numbers of subtests: each of the subtests in customized-built-in-constructor-exceptions.html would be worth 10%, and each element in builtin-coverage.html (each with four subtests) would be worth 0.45%.

@gsnedders gsnedders mentioned this issue Oct 25, 2022
Closed
@josepharhar
Copy link
Author

I just added the pseudo-class-defined.html and custom-elements/parser/ tests to this issue because they are only failing in safari and only due to custom builtins.

@foolip
Copy link
Member

foolip commented Nov 11, 2022

In the MDN short survey on APIs & JavaScript, "Web Components (custom elements, Shadow DOM, etc.)" was the most popular choice by a fairly wide margin, selected by ~39% of survey takers.

Web Components was split into many granular proposals, and the survey results don't tell us which aspects web developers want the most, but it's fair to say that something about Web Components is important. (I'm posting this comment on each of the split proposals.)

@josepharhar
Copy link
Author

I just moved a bunch of tests from the misc. custom elements proposal into this one: #231 (comment)

@nairnandu
Copy link
Contributor

Thank you for proposing Custom Builtins for inclusion in Interop 2023.

We wanted to let you know that this proposal was not selected to be part of Interop this year. We had many strong proposals, and could not accept them all. Every technology that’s chosen for Interop must have a web standard created from consensus between the parties involved. Custom Builtins does not have such an agreement.

For an overview of our process, see the proposal selection summary. Thank you again for contributing to Interop 2023!

Posted on behalf of the Interop team.

@dgrammatiko dgrammatiko mentioned this issue Feb 9, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
focus-area-proposal Focus Area Proposal
Projects
No open projects
Interop 2023
Status: Proposed
Milestone
No milestone
Development

No branches or pull requests
5 participants
@gsnedders @foolip @domenic @nairnandu @josepharhar