`t19` and threat-related numbering are made permanent by current tooling
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9
- Forks
- 8
- Avg merge
- 14d 42m
- Merged PRs (30d)
- 2
Description
Originally posted by @TallTed and @msporny in https://github.com/w3c/vc-render-method/pull/65#discussion_r3836547631
[@TallTed] This kind of target href forces the
t19and threat-related numbering to be permanent. I would advise rather that this target (and all the neighbor fragment identifiers) drop the x00 from the fragment ID, and use only the name to form the fragment. This will mean renumbering can happen as often as might be needed or wanted, and the links (like this one) will be unbroken.[@msporny] I agree, this is a problem, but it is a problem in the current tooling. I'm also arguing for that in the
respec-threatsextension. I cannot fix that problem now, however, there is much more that needs to change/be updated for that change to go into place.
Issue created for tracking purposes. Hoping we'll get to it in the relatively near future.
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.
Research direction
Start with the linked discussion in pull request 65 and the respec-threats extension, focusing on how target hrefs and neighboring fragment identifiers are generated. Determine the tooling changes needed so renumbering does not break links; done means threat-related anchors can be renumbered without making their identifiers permanent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100