• Onomatopoeia@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      6
      ·
      7 months ago

      I thought all browsers on iOS were just wrappers for the same engine (webkit?), so they really can’t do much there.

        • supermurs@kbin.earth
          link
          fedilink
          arrow-up
          3
          ·
          7 months ago

          Both Vivaldi and Brave have working adblockers on iOS while Firefox does not. This is not WebKit’s fault, shouldn’t be an issue for Firefox mobile developers to implement.

    • ForgottenUsername@lemmy.world
      link
      fedilink
      arrow-up
      6
      arrow-down
      3
      ·
      7 months ago

      Also simply compatibility, some sites just don’t work (or dont work well) on Firefox or librewolf, thats one key reason I go back to brave for a lot of things.

        • ForgottenUsername@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          7 months ago

          Agreed, but I also have work to do. On my personal PC at home I use librewolf, as for most casual browsing its fine.

          But the question was why do people use brave over Firefox and my answer simply is cos it doesn’t have the functionality i need. I dunno about your boss but if I say to mine “I didn’t do my job cos my browser of choice doesn’t work” I don’t reckon I’ll stay employed for long.

      • iAmTheTot@sh.itjust.works
        link
        fedilink
        arrow-up
        6
        ·
        7 months ago

        I genuinely have not seen a site that doesn’t work on Firefox in years. Probably five or more. Can you think of an example off the top of your head?

      • palordrolap@fedia.io
        link
        fedilink
        arrow-up
        5
        ·
        7 months ago

        Name and shame them. Send them a complaint.

        Relatedly, does anyone know if there’s a public list of sites that don’t work (properly or at all) in Firefox somewhere? A quick (non-Google) web search doesn’t seem to turn one up. If I was working at Mozilla, that would be the kind of database I might be interested in making a public resource. And I don’t mean as part of the Bug Tracker, though links between the two for legitimate problems could be useful, I guess.

        Something with a very basic interface that has an offending site name, how it doesn’t work, perhaps why, and what, if anything, Mozilla can do about it. In short simple sentences. One per offending site in 16pt text. And a search feature for when it runs to the hundreds.

        It could be something like: [favicon/logo] example.com - Outright states that it will not support Firefox. Mozilla cannot do anything about this. Complain to Example Inc. [favicon/logo] example.net - interface is buggy in Firefox. Site misuses web standards in a way incompatible with Firefox’s renderer. We are looking into this. <Link to bug tracker here> [favicon/logo] example.org - interface does not load. Site uses non-standard Google-only CSS properties. We are looking into this, but you could also contact The Example Organisation to ask them to review their CSS. etc.

        I’ve not had any problems with the handful of sites I use, at least not outside of something caused by browser security or add-ons which I eventually figured out how to fix.

        That said, I’ve probably forgotten a handful I just straight up refused to visit again when they didn’t work and now they’re not in my regular rotation any more, so I don’t notice.

    • ryan_@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      7 months ago

      This doesn’t solve your same browser issue, but just fyi the browser “Orion” on iOS supports full browser extensions. Its developed by the company that runs the Kagi search engine