MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers
[ElementInternalsType] needs declarative interface
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.4k
- Forks
- 286
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Description
Pleased to see work returning to having the ability to extend builtins but was disappointed no consideration for a declarative interface. It would be unfortunate if the only way to access this capability was via clientside JavaScript. Many use cases do not require client js and it would be good to support progressive enhancement by default. If this isn't considered now it could be very awkward to bolt on later.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No file, test, or entry point is named. Start by reviewing the ElementInternalsType work referenced in the issue and define the declarative interface, its progressive-enhancement behavior, and the acceptance criteria before identifying implementation or specification changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100