I held off on Windows 10 for as long as I could until Adobe, and therefore my job, required it. Now this nonsense. I hope this isn’t the start of them joining on the web DRM bandwagon.

  • JBloodthorn@kbin.social
    92·
    1 year ago

    What’s extra stupid about these, is most of the time just using a user agent switcher to make the site think you’re on chrome or opera makes it work just fine.

    • infamousbelgian@waste-of.space
      21·
      1 year ago

      I do understand it. These are browsers that they decided during development that are not supported. Not supported means not tested by a full QA team for months. And users are generally stupid, soba simple warning (use at your own risk) is something that does not work.

      So they decide to just not support the other browsers.

      To be clear, I am definitely not a fan of Adobe of this mechanism, just explaining.

        • _MusicJunkie@beehaw.orgEnglish
          4·
          1 year ago

          People don’t read warnings. They will still swamp your support department with tickets despite being told their setup is unsupported.

        • boonhet@lemm.ee
          1·
          1 year ago

          You can say browser X may cause issues on the website, but people will still complain that browser X doesn’t work properly and demand you to fix whatever issue they’re having.

    • Big P
      21·
      1 year ago

      I would be surprised if eveything works correctly. Generally they don’t just decide that something isn’t supported for no reason

      • JBloodthorn@kbin.social
        4·
        1 year ago

        Sometimes it’s as simple as something like “firefox doesn’t support import maps”, but now they do (in 108+) but nobody has the time or inclination to go back and validate that the site now works in firefox.