Re: LINK only in HEAD?

2013-12-02 Thread Robin Berjon
On 28/11/2013 23:07 , Ian Hickson wrote: If there are use cases where best practice would involve a in the , we can always change the rules here. I wonder if late loading of secondary style resources (e.g. styles that won't get used in the initial rendering of the page) would qualify here. I

Re: LINK only in HEAD?

2013-11-28 Thread Ian Hickson
On Wed, 27 Nov 2013, Dimitri Glazkov wrote: > On Wed, Nov 27, 2013 at 12:41 PM, Boris Zbarsky wrote: > > > > http://www.whatwg.org/specs/web-apps/current-work/ > > multipage/sections.html#the-body-element says its content model (this > > part is normative!) is > > http://www.whatwg.org/specs/we

Re: LINK only in HEAD?

2013-11-28 Thread Dimitri Glazkov
On Thu, Nov 28, 2013 at 1:49 AM, Ms2ger wrote: > On 11/27/2013 08:44 PM, Dimitri Glazkov wrote: > >> Sure. Nothing precludes the author from using custom elements in HEAD. >> > > Except the HTML parser. Unknown elements imply . Feel free to > use the Live DOM Viewer to confirm that. > DOH. :DG<

Re: LINK only in HEAD?

2013-11-28 Thread Ms2ger
On 11/27/2013 08:44 PM, Dimitri Glazkov wrote: On Wed, Nov 27, 2013 at 11:35 AM, Steve Souders wrote: Is the intention of this example that me-first and me-third occur in the HEAD? Sure. Nothing precludes the author from using custom elements in HEAD. Except the HTML parser. Unknow

Re: LINK only in HEAD?

2013-11-27 Thread Boris Zbarsky
On 11/27/13 3:54 PM, Dimitri Glazkov wrote: I see. Do you know why? Because people wanted to mean something, or something. I really can't say. It seems that all browsers support it anywhere And the spec requires them to, yes. and this looks like just validator hoop-jumping. Sure, li

Re: LINK only in HEAD?

2013-11-27 Thread Dimitri Glazkov
On Wed, Nov 27, 2013 at 12:41 PM, Boris Zbarsky wrote: > > http://www.whatwg.org/specs/web-apps/current-work/ > multipage/sections.html#the-body-element says its content model (this > part is normative!) is http://www.whatwg.org/specs/web-apps/current-work/ > multipage/elements.html#flow-content

Re: LINK only in HEAD?

2013-11-27 Thread Dimitri Glazkov
On Wed, Nov 27, 2013 at 12:19 PM, Steve Souders wrote: > Given that most examples of Custom Elements are visible elements in the > body and the spec doesn't indicate its example is in the HEAD, this example > will likely increase the number of websites that put HTML Import LINK tags > in the body

Re: LINK only in HEAD?

2013-11-27 Thread Boris Zbarsky
On 11/27/13 2:44 PM, Dimitri Glazkov wrote: "If the rel attribute is used, the element is restricted to the head element." This is part of a non-normative content (a note), so I think we're off the hook here :) No. The normative bit is sort of scattered around the spec, but for example: ht

Re: LINK only in HEAD?

2013-11-27 Thread Steve Souders
Given that most examples of Custom Elements are visible elements in the body and the spec doesn't indicate its example is in the HEAD, this example will likely increase the number of websites that put HTML Import LINK tags in the body. This has two downsides: 1. It's flagged as having errors usin

Re: LINK only in HEAD?

2013-11-27 Thread Dimitri Glazkov
On Wed, Nov 27, 2013 at 11:35 AM, Steve Souders wrote: > According to the HTML 4 > specLINK tags must > appear in HEAD: > > *The LINK element may only appear in the head of a document.* > > We probably need something more modern as a refe

LINK only in HEAD?

2013-11-27 Thread Steve Souders
According to the HTML 4 specLINK tags must appear in HEAD: *The LINK element may only appear in the head of a document.* The HTML Imports speccontains the following ex