W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2012

[whatwg] HTMLLinkElement.disabled and HTMLLinkElement.sheet behavior

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 27 Jan 2012 10:44:07 +0100
Message-ID: <4F2271E7.3060408@mit.edu>
On 1/27/12 1:30 AM, Ian Hickson wrote:
> On Wed, 5 Oct 2011, Henri Sivonen wrote:
>> On Tue, Oct 4, 2011 at 9:54 PM, Boris Zbarsky<bzbarsky at mit.edu>  wrote:
>>> What Firefox does do is block execution of<script>  tags (but not
>>> timeouts, callbacks, etc!) if there are pending non-altenate
>>> parser-inserted stylesheet loads.  This is necessary to make sure
>>> that scripts getting layout properties see the effect of those
>>> stylesheets. A side-effect is that a<script>  coming after a<link>
>>> will never see the link in an unloaded state... unless there's a
>>> network error for the<link>  or whatever.
>>
>> One exception: If an inline script comes from document.write(), it
>> doesn't block on pending sheets. It runs right away. If it blocked on
>> pending sheets, the point at which document.write() returns would depend
>> on network performance, which I think would be worse than having
>> document.written inline scripts that poke at styles fail depending on
>> network performance.
>
> Note that this is not conforming. The spec does not currently define any
> such behaviour.

Which part is not conforming?  The exception for alternate sheets, the 
inline script inside document.write thing, or something else?

-Boris
Received on Friday, 27 January 2012 01:44:07 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:10 UTC