MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers
[LinkTagModuleImport] Resolve open issues with importfrom attribute
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.4k
- Forks
- 286
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Description
(The current explainer issue track link to state:open label:LinkTagImportis broken, I used state:open LinkTagModuleImport.)
I think these 2 open issues:
-
Should we attempt to make this feature backward-compatible with classic elements, or are there too many differences?
-
Is href the right way to go, even though it goes through import map processing? Should we use a new attribute such as moduleimport?
could be addressed by a new attribute like importfrom, which is the subject of this comment, in WhatWG issue #12163 "specifier: URL protocol for retrofitting specifiers in places designed for URLs".
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
Start by reviewing the LinkTagModuleImport explainer context, then read the linked comment and WHATWG issue #12163. Compare the backward-compatibility question with the href and importfrom alternatives; done means the open questions have a documented, agreed resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100