speced / speced/respec

Link to attribute value goes to an unrelated definition

Open
#4,435 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
806
Forks
434
Avg merge
1d 21h
Merged PRs (30d)
32

Description

Description of problem

A link to an attribute value is being targeted at an unrelated definition with the same name.

From within the Manifest spec: [^link/rel/manifest^] should link to #link-type-manifest in the HTML spec, but instead links to #dfn-manifest in itself.

URL to affected spec or repo:

https://w3c.github.io/manifest/#updating - see the first sentence there:

As specified for [^link/rel/manifest^] link relation...

What happened (e.g., it crashed)?:

It links to #dfn-manifest, seemingly ignoring the explicit "link/rel" part and just trying to find a definition named "manifest".

Expected behavior (e.g., it shouldn't crash):

It should find the attribute value "manifest" for the attribute "rel" of the element "link", which is defined in HTML at #link-type-manifest.

This works properly for any other type of link, e.g., [^link/rel/stylesheet^]. I think it's getting distracted by the fact that we have a definition of "manifest" in this same document.

See, Respec itself tells me to cite it using this syntax (and it says to use [=manifest=] to get the other definition):

image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Respec's reference-link resolution for the [^link/rel/manifest^] syntax and compare it with the working [^link/rel/stylesheet^] case. Done means the Manifest spec reference resolves to HTML's #link-type-manifest definition rather than the local #dfn-manifest definition.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.