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

[Bug 12145] define how to resolve conflicting link types

From: <bugzilla@jessica.w3.org>
Date: Mon, 21 Feb 2011 09:43:59 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PrSJD-00079v-0Y@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12145

Philip Jägenstedt <philipj@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |philipj@opera.com
         Resolution|                            |INVALID

--- Comment #1 from Philip Jägenstedt <philipj@opera.com> 2011-02-21 09:43:58 UTC ---
Hmm, I wanted to write some examples here in response to
<http://lists.w3.org/Archives/Public/public-html/2011Feb/0345.html>, but all I
could come up with in the existing list of keywords is:

<link rel="prev" href="foo.html">
<link rel="next" href="foo.html">

It turns out this isn't really a conflict, it would just result in a circular
reference of sorts, which is silly but not something implementations need to
handle.

<link rel="next" href="foo.html">
<link rel="next" href="bar.html">

This is not a conflict between the link types, but rather a question of which
document would be navigated to if one follows the "next" button in a browser.
That should be defined, but is unrelated to the problem I tried to formulate.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 21 February 2011 09:44:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 21 February 2011 09:44:00 GMT