the rel=import LINK tags can be placed in the BODY near the
web component to reduce render blocking.
-Steve Souders
-without-execution/) by
Stoyan Stefanov, which describes how to download JavaScript without
execution it, as a cache-warming technique.
2. ControlJS (http://stevesouders.com/controljs/) by Steve Souders,
which extends Stoyan's model to allow on-demand execution of scripts.
3. Gmail putting JavaScript
describes how to download JavaScript without
execution it, as a cache-warming technique.
2. ControlJS (http://stevesouders.com/controljs/) by Steve Souders,
which extends Stoyan's model to allow on-demand execution of scripts.
3. Gmail putting JavaScript in comments and then parsing later
(http
be downloaded some time
2000ms. Since it's loaded earlier, it steals a network connection and
causes one of the images to download later.)
-Steve
On 7/23/2010 1:27 PM, Ian Hickson wrote:
On Wed, 17 Mar 2010, Steve Souders wrote:
Given that it is possible to do this from script, how common
behaving.
If we do want to do something like this, one possibility would be to
create a generic attribute that can go on things likeimg,link
rel=stylesheet,script etc that make the resource not block the
'load' event.
On Thu, 11 Feb 2010, Steve Souders wrote:
I just sent email last week
Sicking
Cc: Steve Souders; WHAT Working Group
Subject: Re: [whatwg] should async scripts block the document's load event?
Right. Async scripts aren't really asynchronous if they block all the
user-visible functionality that sites currently tie to window.onload.
I don't know if we need another
I just sent email last week proposing a POSTONLOAD attribute for scripts.
-Steve
On 2/10/2010 5:18 PM, Jonas Sicking wrote:
On Fri, Nov 6, 2009 at 4:22 PM, Brian Kuhnbnk...@gmail.com wrote:
No one has any thoughts on this?
It seems to me that the purpose of async scripts is to get out of
Zbarsky wrote:
On 2/8/10 4:54 PM, Steve Souders wrote:
4. If the element has a src attribute, [snip] the specified resource
must then be fetched, from the origin of the element's Document.
If the script has DEFER, the request should not start until after
parsing is finished. Starting it earlier could
the optimization.
- 3rd parties have no control over where their snippet is placed in
the content owner's page. Providing a snippet that contains DEFER will
guarantee they don't block the main page's content.
-Steve
On 2/10/2010 1:31 AM, Henri Sivonen wrote:
On Feb 8, 2010, at 23:54, Steve Souders
is significantly simpler than adding a load handler that
dynamically appends a SCRIPT element to the DOM.
-Steve
On 2/9/2010 6:40 PM, Boris Zbarsky wrote:
On 2/8/10 5:06 PM, Steve Souders wrote:
The behavior would be similar to DEFER, but instead of delaying
downloads until after parsing
I'd like to propose the addition of a POSTONLOAD attribute to the SCRIPT
tag.
The behavior would be similar to DEFER, but instead of delaying
downloads until after parsing they would be delayed until after the
window's load event. Similar to DEFER, this new attribute would ensure
scripts
I have some comments and questions about the ASYNC and DEFER attributes
of the SCRIPT tag based on reading this document:
http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html
http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html#script
1. If
12 matches
Mail list logo
