• Sam Dutton

    Thanks so much for all the questions on live chat!

    If you have more questions, add them here on Twitter with the hashtag #AskChrome.


  • Rick Beacham

    newb question – You said video is processed through the GPU and images
    are processed through the CPU. I'm curious if there is way to easily
    process images via the GPU?

  • basan

    Do one about video please. I really want to know if its possible to have WebM with alpha with gpu accelerated compositing (currently it's very CPU intensive). And on that note HAP Video would be awesome if making webM+alpha more GPU bound isn't possible.

  • Fred M.

    Thank you Chrome developers! Learned a few things 🙂 I hope webp will be supported soon on Safari so no more fallbacks. Looking forward to your next video!

  • rikithikatakizu2

    I enjoy your channel, and continuously learn from you. That's great, i really appreciate your work!
    And that new rubric is also nice and interesting.

  • Orchard Matthew

    Is there a way to test for support of native image lazy loading? That way we can fallback to a JS solution if the users browser doesn't support the new attribute.

  • Geoff James

    Great video, guys! Really enjoyed this. Looking forward to more episodes.

    I'm using the loading="lazy" attribute myself, and getting the warning about no dimensions (width/height) specified, so it was refreshing to hear Yoav mention about the width/height properties being used for reflow with lazy loaded images.

    Just to clarify – if I don't know the exact dimensions of an image in the viewport (as it's responsive), will the width/height attribute help Chrome define the implicit aspect ratio of images? So, if I knew my image was 4:3, I could set the width and height attributes to 100/75 respectively and Chrome would know to expect a 4:3 image; but the CSS would take care of the actual image size in the viewport.

    Thanks again, guys! 😁

Leave a Reply

Your email address will not be published. Required fields are marked *