[whatwg] Small consistency issue with HTML5 nav element examples
svartman95 at gmail.com
Tue Jan 25 08:28:50 PST 2011
On 1/24/11, Ian Hickson <ian at hixie.ch> wrote:
> On Mon, 24 Jan 2011, Bjartur Thorlacius wrote:
>> But then, when should hyperlinks be created with <link>s?
> More or less never. <link> links don't show on most Web browsers.
IMO browsers should implement <link>. <link> should be implementable
cross-browser in CSS.
>> And what happened to @rel=related being the default relation?
> Not sure to what you are referring.
Sorry, my memory failed me. There is no default relation in HTML 4.
>> Navigation links are clearly metadata, belonging to <head>.
> How do you distinguish what is data vs what is metadata?
Generally, I categorize everything which isn't mentioned in the <title>
or Content-Description (or would be, as there's usually none). No
document would be described as "
My actual concern regard navigation links not forming a part of the linear
body of the document, but still being in <body>. Navigation links will
most likely be rendered "out of band," potentially only on demand and
paged/scrolled seperately from the body, or at the end of the document in
one dimensional renderings (such as audio and text streams). They might
even be triggered without being rendered at all, such as by scrolling out
of range of the current document.
>> For the record links and links2 render all hyperlinks (including ones
>> with unrecognized values of @rel).
More information about the whatwg