- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 12 Mar 2013 10:46:34 +0000
- To: Dimitri Glazkov <dglazkov@google.com>
- Cc: public-webapps <public-webapps@w3.org>
On Mon, Mar 11, 2013 at 8:00 PM, Dimitri Glazkov <dglazkov@google.com> wrote: > The resources will only block script (just like CSS: > https://www.w3.org/Bugs/Public/show_bug.cgi?id=21218), so there's definitely > opportunity for parallelism. Blocking script for CSS is seen as a large pita and I've heard requests for ways to prevent that (e.g. with <link rel=stylesheet async>). Expanding the set of external resources that does that does not seem like a great idea to me. > I am not sure how the message port thing will work. Never mind that suggestion. We can't have an async DOM (yet). > b) making sub-resources not block on script sort of ruins my plan for > integrating <element> registration. If there's no blocking script, I have no > assurances that the <element>s in subresources are registered before script > starts running, which means that we'll have to do something like element > upgrade, which I worked pretty hard to remove :) I recommend discussing this with the HTML parser crowd and performance crowd. I would've thought we would not want to repeat mistakes made in the past. -- http://annevankesteren.nl/
Received on Tuesday, 12 March 2013 10:47:02 UTC