Teams also doesn’t support multiple “work” accounts, so I had to boot up a laptop to accept the call. 🤷

  • drathvedro@lemm.ee
    link
    fedilink
    English
    arrow-up
    13
    ·
    11 months ago

    Feature detection is usually the way to go. If your website / webapp depends on a particular feature, check if that specific feature exists, rather than checking for particular browsers. Browser checks are still needed in some cases, for example Safari sometimes reports that it supports particular features but it really doesn’t (or they’re so buggy to the point where they’re unusable), but that’s relatively rare.

    This is tough to implement when the feature is present, but implemented wrong. Or, even worse, when it’s implemented right, but the most popular browser implements it wrong and almost everyone else follow suit for compatibility reasons, except for one that takes the stance of following standards. I know safari is notorious for this, think pale moon had those issues, too, and there are still echoes from the past from pre-chrome internet explorer, thank god it’s finally dead.

      • dan@upvote.au
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        3
        ·
        11 months ago

        At least Chrome is mostly standards-compliant and doesn’t do anything too weirdly. I’d say Safari is the new IE - lots of weird bugs that no other browser has, and sometimes you need hacks specific to Safari.

        • Monument@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          2
          ·
          11 months ago

          That’s fair. I meant that more in terms of using market dominance to shape the browser market, and not in entirely good ways.

          I’ll rue the day that every website insists it only works with Chrome because of some user-privacy degrading feature that Google insists is a core web technology.