This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25697 - [imports]: why can imports be sync?
Summary: [imports]: why can imports be sync?
Status: RESOLVED WORKSFORME
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20683
  Show dependency tree / graph
 
Reported: 2014-05-13 21:57 UTC by Ian 'Hixie' Hickson
Modified: 2014-05-14 18:56 UTC (History)
3 users (show)

See Also:

Attachments

Description Ian 'Hixie' Hickson 2014-05-13 21:57:26 UTC 
"an import that is blocking scripts"

Isn't this exactly the kind of thing we learnt from style sheets we should never do? Making anything synchronous will just make performance worse, no?

Isn't the best practice going to be to make them async and then have code handle the components and stuff coming in later? e.g. the way Google+ loads a static version of itself and then fixes itself up so that it loads "REALLY FAST" but isn't actually interactive until sometime after it's loaded?

Why not make them all async?
Comment 1 Ian 'Hixie' Hickson 2014-05-14 18:56:44 UTC 
Spoke with dglazkov. It's only legacy <script> elements that are sync. <script type=module>, <script> inside rel=import files, style sheets, and other <link>s, are not blocked.