- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 28 Jun 2013 16:04:02 -0700
- To: Felipe Nascimento de Moura <felipenmoura@gmail.com>
- Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, www-style <www-style@w3.org>, brice@websailors.fr
On Fri, Jun 28, 2013 at 2:47 PM, Felipe Nascimento de Moura
<felipenmoura@gmail.com> wrote:
> Hi.
> Yes, that's true, although most of(if not 99%) implementations "out there"
> do it the bad way :/
> Brice Parent gave another interesting idea, of using
> async="none|async|postponed|..." in loadable elements(such as images,
> object, video, iframe...) as an attribute, like
> <img src="photo.png" alt="photo!" postponed/>
Please don't "top-post". <http://wiki.csswg.org/tools/www-style>
> In this case, I believe we should discuss it with HTML list's people, right?
Yup, and I think there's already been some discussion about that.
Send mail to <whatwg@whatwg.org>.
> Also, it would be really interesting to use as another background
> characteristic, as proposed by Sebastian Zartner.
> Like
> background-image: url(mygreatestphoto.jpg) postponed;
> or
> background-load-method: postponed;
>
> With that, we would even be able to say that:
>
> body.mobile div{
> background-load-method: postponed;
> }
>
> this way, a server side application could write the body tag with or without
> the "mobile" class, therefore, all the div elements with background images
> would be postponed to load their background.
Yeah, I'm potentially interested in pursuing something to indicate a
lazy-loaded image in CSS as well. We can bake it into image(), which
is designed to have its set of annotations expanded over time.
"background-image: image(defer "foo.jpg");" or the like.
~TJ
Received on Friday, 28 June 2013 23:04:48 UTC