zachleat’s avatarzachleat’s Twitter Archive—№ 22,666

          1. I just learned a new thing about web font loading and I’m super pumped up about it. Learning is fun 🕺
            Permalink On twitter.com Twitter logo zachleat’s avatar ♻️ 7 Retweets ❤️ 33 Favorites Mood +7 🙂
        1. …in reply to @zachleat
          Here’s what I’m looking at here—how do the web fonts render while this page loads?
          oh my god twitter doesn’t include alt text from images in their API
          Permalink On twitter.com Twitter logo zachleat’s avatar ♻️ 1 Retweets ❤️ 14 Favorites Mood 0
      1. …in reply to @zachleat
        Pretty sure I found bugs in both Firefox and Chrome while testing this. Safari, you’re cool (thanks be to @Litherum)
        Permalink On twitter.com Twitter logo zachleat’s avatar ♻️ 2 Retweets ❤️ 15 Favorites Mood +4 🙂
    1. …in reply to @zachleat
      Without unicode-range, Firefox requests both web fonts in parallel. Chrome/Safari correctly request fallback sequentially after the subset has loaded. It should wait for the first web font to load to know what code points available in the file and if the fallback is needed.
      oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API
      Permalink On twitter.com Twitter logo zachleat’s avatar ♻️ 3 Retweets ❤️ 6 Favorites Mood 0
  1. …in reply to @zachleat
    I have no idea what Chrome is doing here. It renders the div h1 first, when the subset has loaded and then waits for the fallback to render the h1. They should render at the same time—they have the same content. Why Chrome? Why? 😱
    oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API
    On twitter.com Twitter logo zachleat’s avatar ♻️ 1 Retweets ❤️ 4 Favorites Mood -1 🙁