The upgrade step of custom elements are missing in the `define` page ?
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- html, javascript
- Domain
- documentation, web-dev
Research direction
Start with the MDN CustomElementRegistry.define Description section and compare its step 18 reference with the WHATWG custom-elements specification. Review the existing CustomElementRegistry.upgrade documentation, then add a concise, accurate explanation of the relevant upgrade behavior and verify the wording against the specification.
Written by the indexing model from the issue text.
Description
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry/define#description
What specific section or headline is this issue about?
Description
What information was incorrect, unhelpful, or incomplete?
Step - 18, I think thats how most of the custom elements get consumed (?) , the browser upgrades the custom element , https://html.spec.whatwg.org/multipage/custom-elements.html#dom-customelementregistry-define ,
ik , this exists https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry/upgrade#description , but I dont really know, I feel like 1 or 2 lines about upgrade should be there. Eg - the constructor should be run and connectedcallback also should be run.
Can I send a PR ?
What did you expect to see?
A few lines about the upgrade event
Do you have any supporting links, references, or citations?
https://html.spec.whatwg.org/multipage/custom-elements.html#dom-customelementregistry-define step 18
Do you have anything more you want to share?
No response
- Dominant language
- Markdown
- Stars
- 11k
- Forks
- 23.3k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 311
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mdn/content
-
Content:Learn:CSS good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
accepting PR Content:WebAPI
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
area: WebAuthn Content:WebAPI
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Content:WebExt
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Content:HTML needs info
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100