Chronotope’s avatarChronotope’s Twitter Archive—№ 102,246

                    1. With Chrome soon lazy loading iframes by default there are going to be some publisher advertising folks who will be very surprised by sudden and serious drops in programmatic CPMs and direct sold inventory. It's going to be a bad Q3 in ad tech y'all.
                      Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 28 Retweets ❤️ 80 Favorites Mood -4 🙁
                  1. …in reply to @Chronotope
                    For those of us who built right and accurate lazy loading systems, things will be better. But consider this: most ads have iframes in them and when have agencies ever been fast to pick up new technological requirements?
                    Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 2 Retweets ❤️ 10 Favorites Mood +1 🙂
                1. …in reply to @Chronotope
                  Also, Firefox is on the same train. zdnet.com/article/after-chrome-firefox-will-also-support-off-screen-image-lazy-loading/
                  OpenGraph image for zdnet.com/article/after-chrome-firefox-will-also-support-off-screen-image-lazy-loading/
                  Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 4 Favorites Mood 0
              1. …in reply to @Chronotope
                wheeeeeee
                Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 10 Favorites Mood 0
            1. …in reply to @Chronotope
              Intent to ship is over here: groups.google.com/a/chromium.org/forum/m/#!msg/blink-dev/jxiJvQc-gVg/wurng4zZBQAJ
              OpenGraph image for groups.google.com/a/chromium.org/forum/m/#!msg/blink-dev/jxiJvQc-gVg/wurng4zZBQAJ
              Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood 0
          1. …in reply to @Chronotope
            If you manage ad ops for your publication, have them download Canary, flip the flag on, and start testing.
            Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 2 Favorites Mood 0
        1. …in reply to @Chronotope
          (or at least queue that up in your project management system) I'll be very interested to hear about the impact via people giving anonymous interviews to Digiday.
          Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 3 Favorites Mood +2 🙂
      1. …in reply to @Chronotope
        Anyway, this is an overall good thing, but like most good things in ad tech, and especially in respect to how they impact publishers, it'll hurt before it heals. Chronotope/1115234782148014082/photo/1
        Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 2 Favorites Mood +8 🙂
    1. …in reply to @Chronotope
      Test for yourself - gist.github.com/AramZS/b5b46f4dc2b2cd9d525a1b912722a096 adopted from github.com/scott-little/lazyload
      OpenGraph image for gist.github.com/AramZS/b5b46f4dc2b2cd9d525a1b912722a096OpenGraph image for github.com/scott-little/lazyload
      Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood 0
  1. …in reply to @Chronotope
    Deleted some tweets that were incorrect, did a quick re-test to confirm and fixed some mistaken parameters. iFrames that are set to loading='eager' do indeed seem to pass that to internal elements, so that's a relief.
    On twitter.com Twitter logo Chronotope’s avatar Mood -2 🙁
    1. …in reply to @Chronotope
      Publishers are still likely to experience a serious impact, but at least that means that we don't have to force every single agency to alter their creatives. Will have to do more testing around iFrames inside of iFrames to see what occurs, as that is unfortunately not uncommon.
      Permalink On twitter.com Twitter logo Chronotope’s avatar Mood 0

Search tweets' text