- From: Hiroshi Kawada <kawada.hirosi@gmail.com>
- Date: Tue, 12 May 2015 17:14:29 +0900
- To: Nik Matsievsky <speed@webo.name>
- Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
- Message-ID: <CAMK1dyOeTiOH-mz7xC0uX7PHqVTKH-+p2DMD5O5tPpPc-W4xOg@mail.gmail.com>
> Lazyload attribute is similar to the part of HTTP 2 features. Server Push in HTTP2 covers the use case of lazyload attribute. So it's not adaptive for Web Developers, if HTTP 2 implementation is earlier than lazyload attribute. On Tue, May 12, 2015 at 9:47 AM, Hiroshi Kawada <kawada.hirosi@gmail.com> wrote: > Hi > > It's very nice argue! > > Postpone/Lazyload attributes are very useful for ATF performance > optimization. I also want to use it without jQuery-Lazyload Libraries. > Postpone attribute is an anti-pattern on mobile, so it should be > deprecated. But Lazyload attribute is not so bad for mobile network. > > Lazyload attribute is similar to the part of HTTP 2 features. But they are > used by different roles. > > > On Sat, May 9, 2015 at 4:39 AM, Nik Matsievsky <speed@webo.name> wrote: > >> Ilya, thank you for clarification. >> >> Who knows is there any (coming) specifications about lazyload feature >> (for images / media files)? It's quite useful for heavy websites. >> >> Hey Evgeniy. >> >> Sorry about the confusion! The Resource Priorities spec is, indeed, >> deprecated. I'll see if we can update the w3.org doc to make this clear >> -- thanks for the heads up. Also, I'm not aware of any plans by other >> browsers to support "lazyload". >> >> >> >> -- >> Thank you, Nik Matsievsky >> WEBO Software, www.webogroup.com+7 926 7281964, skype:nikolay.matsievsky >> >> > > > -- > KAWADA Hiroshi > Web Developer (JPN) > http://hiroshik.info/ > -- KAWADA Hiroshi Web Developer (JPN) http://hiroshik.info/
Received on Tuesday, 12 May 2015 08:14:57 UTC