W3C home > Mailing lists > Public > public-web-perf@w3.org > December 2013

Re: [minutes] Web Performance WG Teleconference #122 2013-12-11

From: Ilya Grigorik <igrigorik@google.com>
Date: Wed, 11 Dec 2013 20:09:08 -0800
Message-ID: <CADXXVKrC8ebNd3_wiy3ZfLEOku9e8XeWNw=UW2_T265qyU+hDA@mail.gmail.com>
To: Jatinder Mann <jmann@microsoft.com>
Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
On Wed, Dec 11, 2013 at 5:54 PM, Jatinder Mann <jmann@microsoft.com> wrote:

> Ilya also raised a concern that postpone should be able to be set on
> container elements that arenít visible, like the div element. This way
> users can set postpone on the container instead of setting it on each
> individual element. Seeing that using CSS wonít work as formatting occurs
> much later in the pipeline, this seems like a reasonable request.

To provide a bit more context, the case I had in mind is something like

<div id="header"> ... </div>
<div id="hero-content" *postpone*>
   <img src="large-image.jpg">
   <script src="awesome-widget.js">
<my-awesome-future-component *postpone*>
  <li> Foo
  <li> Bar
</div id="footer"> ... </div>

When designing an RWD site it's fairly common to hide (display: none) an
entire section (e.g. the big "hero" section in example above), which may
contain images, scripts, and other external resources. Today, you would
have to put a "postpone" attribute on every element within that container,
and even with that you wouldn't be able to postpone a script or any other
element that's not part of the render tree.

Instead, I'm wondering if we can allow postpone to be defined not just on
an individual element but on a containing element, which would then
propagate this state to all of its children - i.e. in example above,
neither large-image.jpg or awesome-widget.js would get downloaded while
#hero-content is not part of the rendering tree. I think this would make
RWD development a lot simpler... and lighter.

As a case in point, I've seen many sites which hide maps script or social
widgets sections until they are clicked and expanded (and often they're
not) - today, those scripts are still downloaded, whereas allowing postpone
on an outer container would load them on demand or not at all.


P.S. we should also think about how this could/would interact with custom
Received on Thursday, 12 December 2013 04:10:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:37 UTC