W3C home > Mailing lists > Public > public-html@w3.org > July 2009

RE: [HTML5] DOMContentLoaded fires before CSS resources loaded?

From: Travis Leithead <travil@microsoft.com>
Date: Fri, 24 Jul 2009 02:14:15 +0000
To: Boris Zbarsky <bzbarsky@MIT.EDU>, Maciej Stachowiak <mjs@apple.com>
CC: "public-html@w3.org" <public-html@w3.org>, Jacob Rossi <t-jacobr@microsoft.com>, Kirk Sykora <ksykora@microsoft.com>, Harley Rosnow <Harley.Rosnow@microsoft.com>
Message-ID: <49142F02149340458FDD20841AD0AD560623B8@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> 
Thanks for that clarification. I'm curious what web compatibility issues motivated the change? Any pointers?

-----Original Message-----
From: public-html-request@w3.org [mailto:public-html-request@w3.org] On Behalf Of Boris Zbarsky
Sent: Wednesday, July 22, 2009 8:48 PM
To: Maciej Stachowiak
Cc: Travis Leithead; public-html@w3.org; Jacob Rossi; Kirk Sykora; Harley Rosnow
Subject: Re: [HTML5] DOMContentLoaded fires before CSS resources loaded?

Maciej Stachowiak wrote:
> However, if we encounter a <script> element while a stylesheet load is
> pending, we block parsing until the stylesheet is loaded.

This is precisely what Gecko does (and my apologies for mis-stating what Webkit does in my previous mail; I think it's pretty clear that both have been changing how this works recently....)

-Boris
Received on Friday, 24 July 2009 02:15:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:40:37 GMT