you are viewing a single comment's thread
view the rest of the comments
[–] 205 points 6 months ago (20 children)

Well your first mistake was using Chrome in 2026

  • source
  • hideshow 20 child comments
  • [–] 29 points 6 months ago (15 children)

    I hate that I still have to use Chrome because it can do some streaming stuff better than Firefox (and even Chromium for some reason). I only use it to connect to one KVM.

  • source
  • parent
  • hideshow 15 child comments
  • [–] 81 points 6 months ago (10 children)

    Do the streaming issues resolve themselves ✨magically✨ when faking the user agent to be Chrome for those streaming sites, e.g. using Firefox and a user agent add-on?

  • source
  • parent
  • hideshow 10 child comments
  • [–] 32 points 6 months ago (3 children)

    Many do, yes. Any time I get an error message like "You're not using a supported browser" that message vanishes after adjusting the user agent.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 8 points 6 months ago (2 children)

    Well yes, the warning messages will disappear as those are often shown or not shown based on user agent.

    But will the actual streaming issues go away is the big question.

    Teams on the web for example, worked fine in Firefox even though it warned the user it didn't work in anything but Chrome.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 15 points 6 months ago (3 children)

    My issues were with h265/HEVC support, proprietary stuff like media codecs can sometimes be a pain. I no longer have that need so I'm a happy fox.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 7 points 6 months ago (2 children)

    Pretty sure Firefox added support for HEVC a while back, but it relies on the system to provide the decoder (Which you'll usually have to pay extra for)

    Firefox also supports MKV files now, which is nice.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 5 months ago (1 child)

    Firefox also supports MKV files now, which is nice.

    Since when‽ It feels like support for that format took centuries!

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 5 months ago*

    In 145.

    Funny thing is, the WebM format is actually a constrained profile of MKV, and Firefox strictly enforced those compatibility checks. Chrome never did though, so it could always support MKV files but only if you lied and claimed they were WebM.

    Edit: Lemmy eats the highlight in the link, look for "Matroska" under "Web Platform"

  • source
  • parent
  • [–] 5 points 6 months ago* (last edited 6 months ago) (3 children)

    For when I need Chrome, I use Vivaldi. Its probably over bloated for what I need, but it works.

  • source
  • parent
  • hideshow 3 child comments
  • When I need to use Chrome, I just use the Chrome Mask extension in Firefox to change my user agent. I haven’t had a site that actually failed to work on the Gecko engine instead of Chromium. It’s just lazy devs checking your user agent to see if you’re using Chromium, and then throwing a fit if you’re not.

    Chrome Mask even has a built in site reporter, because broken sites don’t actually conform to modern web interoperability requirements. If it fails to work on Gecko, there’s a good chance that it will also fail to work on other platforms (like Apple’s WebKit) as well. And the reports go to the team that develops Firefox, so they can figure out why the site is refusing to work on Gecko.

  • source
  • parent
  • [–] 1 point 6 months ago

    Vivaldi is a great Chromium browser. I'm more of a Firefox/Librewolf on my personal machines, but my work's software has a few features that only work with Chromium extensions so I had to use it. Was my preferred alternative to all others, while bloated it was highly controllable and didn't focus on unnecessary features like Brave or others. My work recently banned any browser that isn't Chrome/Edge/Firefox though, so I guess I'm back to Firefox and will ignore the features I can't use

  • source
  • parent