Chronotope’s avatarChronotope’s Twitter Archive—№ 146,026

        1. lol 1. I'm not using Chrome. 2. The 96.0.4664 version of Chrome is a *mere* 4 months old. This seems a little aggressive Bloomberg, considering there are sites still stuck supporting IE6. I think you can maintain backward support for versions less than a year old, no?
          oh my god twitter doesn’t include alt text from images in their API
      1. …in reply to @Chronotope
        I'm actually a little jealous. I wish I could get away professionally with not supporting any browser older than 4 months (only 2 major version numbers from current Chrome!), good on whatever engineer managed to get away with that over at Bloomberg.
    1. …in reply to @Chronotope
      The current production channel is 98.0.4758! What could possibly be so far out of date as to break support I wonder? Arrays sorting slower? COLRv1 fonts? CORS preflight?
  1. …in reply to @Chronotope
    In case you were wondering, I was indeed able to read the article and interact with the site.
    1. …in reply to @Chronotope
      I'm going to bet that this warning isn't actually about my browser version, but instead triggered by some sort of feature detection hooked on to some feature that they use for ads but that Vivaldi has blocked in such a way for privacy reasons that the site thinks it isn't there.


Search tweets' text