Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define the the term “the external resource is to be applied” #2503

Closed
sideshowbarker opened this issue Apr 4, 2017 · 1 comment
Closed

Comments

@sideshowbarker
Copy link
Contributor

https://html.spec.whatwg.org/multipage/semantics.html#the-link-element says:

The exact behavior for links to external resources depends on the exact relationship, as defined for the relevant link type. Some of the attributes control whether or not the external resource is to be applied (as defined below).

…but the term “the external resource is to be applied” is not clearly defined—not with a dfn anywhere, but also not otherwise defined in prose that makes it immediately obvious what it means.

I can create a PR for this but it’s probably best to wait until we wrap up #2354 and merge it.

sideshowbarker added a commit that referenced this issue Apr 6, 2017
The section of the spec that provide details about attributes for the
`link` element contains the following statement:

> Some of the attributes control whether or not the external resource is
> to be applied (as defined below).

This change drops that statement.

That statement has been in the spec for 11 years but isn’t stating a
normative requirement nor serving any useful purpose—instead, it’s
actually just distracting and counter-productive in that despite saying
“as defined below”, the notion of “to be applied” isn’t actually clearly
defined at all in the prose anywhere in the spc below that statement.

Fixes #2503
@sideshowbarker
Copy link
Contributor Author

So I dug back into the history of that statement in the spec but found that it’s been that way unchanged since it was first added 12 years ago https://web.archive.org/web/20050301091946/http://whatwg.org/specs/web-apps/current-work/

It’s not a necessary statement and upon consideration doesn’t seem to be serving any useful purpose; it adds nothing as far as clarification on the rest of the content in that section—in fact, it distracts from the rest of the content in that it leads a (careful) reader to expect something substantive about external resources being “applied” to be clearly defined in the spec text that follows. But the spec text that follows doesn’t provide that, so it seems better to just drop that sentence altogether, which is what #2513 does.

domenic pushed a commit that referenced this issue Apr 11, 2017
The section of the spec that provide details about attributes for the
link element contains the following statement:

> Some of the attributes control whether or not the external resource is
> to be applied (as defined below).

This change drops that statement.

That statement has been in the spec for 11 years but isn’t stating a
normative requirement nor serving any useful purpose—instead, it’s
actually just distracting and counter-productive in that despite saying
“as defined below”, the notion of “to be applied” isn’t actually clearly
defined at all in the prose anywhere in the spc below that statement.

Fixes #2503.
inikulin pushed a commit to HTMLParseErrorWG/html that referenced this issue May 9, 2017
The section of the spec that provide details about attributes for the
link element contains the following statement:

> Some of the attributes control whether or not the external resource is
> to be applied (as defined below).

This change drops that statement.

That statement has been in the spec for 11 years but isn’t stating a
normative requirement nor serving any useful purpose—instead, it’s
actually just distracting and counter-productive in that despite saying
“as defined below”, the notion of “to be applied” isn’t actually clearly
defined at all in the prose anywhere in the spc below that statement.

Fixes whatwg#2503.
inikulin pushed a commit to HTMLParseErrorWG/html that referenced this issue May 9, 2017
The section of the spec that provide details about attributes for the
link element contains the following statement:

> Some of the attributes control whether or not the external resource is
> to be applied (as defined below).

This change drops that statement.

That statement has been in the spec for 11 years but isn’t stating a
normative requirement nor serving any useful purpose—instead, it’s
actually just distracting and counter-productive in that despite saying
“as defined below”, the notion of “to be applied” isn’t actually clearly
defined at all in the prose anywhere in the spc below that statement.

Fixes whatwg#2503.
alice pushed a commit to alice/html that referenced this issue Jan 8, 2019
The section of the spec that provide details about attributes for the
link element contains the following statement:

> Some of the attributes control whether or not the external resource is
> to be applied (as defined below).

This change drops that statement.

That statement has been in the spec for 11 years but isn’t stating a
normative requirement nor serving any useful purpose—instead, it’s
actually just distracting and counter-productive in that despite saying
“as defined below”, the notion of “to be applied” isn’t actually clearly
defined at all in the prose anywhere in the spc below that statement.

Fixes whatwg#2503.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant