W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

[Bug 25697] New: [imports]: why can imports be sync?

From: <bugzilla@jessica.w3.org>
Date: Tue, 13 May 2014 21:57:26 +0000
To: public-webapps@w3.org
Message-ID: <bug-25697-2927@http.www.w3.org/Bugs/Public/>

            Bug ID: 25697
           Summary: [imports]: why can imports be sync?
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: ian@hixie.ch
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org
            Blocks: 20683

"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?

You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 13 May 2014 21:57:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:24 UTC