W3C home > Mailing lists > Public > public-html@w3.org > February 2011

Re: combining relations from multiple link elements, (see also ISSUE-124)

From: Maciej Stachowiak <mjs@apple.com>
Date: Mon, 21 Feb 2011 17:07:02 -0800
Cc: Philip Jägenstedt <philipj@opera.com>, public-html@w3.org
Message-id: <23B0C5C2-8AA6-427E-80F4-64C9F70B921B@apple.com>
To: Julian Reschke <julian.reschke@gmx.de>

On Feb 21, 2011, at 2:27 PM, Julian Reschke wrote:

> On 21.02.2011 22:48, Philip Jägenstedt wrote:
>> ...
>>> It seems like the issue here is:
>>> 
>>> - Some <link> types (e.g. stylesheet, icon) can passively trigger
>>> loads, which are combined when loading the same resource.
>>> - <a> links only load something when explicitly activated by the user,
>>> so there is no issue of combining loads.
>>> - noreferrer alters loading behavior.
>>> 
>>> As a result, noreferrer has clear behavior on <a>, but not necessarily
>>> on <link>.
>> 
>> Yes, that is precisely the problem I am describing.
>> ...
> 
> The problem is that link relations can put conflicting semantics on a link. This is not specific to link/@rel)nofollow. It could happen on a/rel as well. I don't see how the instantiation semantics affect the overall issue.

I believe the problem with noreferrer that Philip has identified is a question of implementation behavior, not semantics. Most link relations do not alter loading behavior, and therefore do not have this issue. 

You may be right that conflicting semantics are another potential issue, but that's separate from this implementation behavior issue that is specific to noreferrer. To you, this may seem like a subset of an issue about semantics, but to implementors it is likely to seem like a separate issue.

Regards,
Maciej
Received on Tuesday, 22 February 2011 01:08:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:22 UTC