I've been using Mozilla browsers since NetScape Navigator. I'll probably have to stop soon...

I've been using Mozilla browsers since NetScape Navigator. I'll probably have to stop soon. Firefox is just too buggy and incomplete.

The attitude of the developers on Bugzilla is just *horrendous*. Users take their time to submit detailed reports, with repro steps, explanations, references, and screenshots of how other browsers behave. These tickets will sit in the queue for *decades*, sometimes with thousands or even tens of thousands of "me too!" and "is this fixed yet?" comments. The only response you will see from anyone at Mozilla is internal paper-pushing. Assigning of categories, merging bugs, assigning to a team, or whatever. Almost never will you see an actual developer *fix* the issue.

Currently, Firefox the only major browser that:
>Doesn't consistently support colour management.
>Doesn't support HDR on sites like YouTube.
>Doesn't pick up the operating system PKI trust store.
>Doesn't play nice with Enterprise deployment and configuration management.

... etc ...

The core team has lost its way and is too busy playing with stupid pet projects with no business value. The CPO should really start knocking some heads together and start asking tough questions like:

- Why are there open bug tickets old enough to drink and have little bugs of their own?
- Why is Firefox unable to correctly view content on the #1 video site in the world?

Etc...


Fix the basics!

Attached: 1639569534545.png (481x500, 303.21K)

Other urls found in this thread:

github.com/mozilla/policy-templates
theregister.com/2021/10/04/chrome_breaks_web/
support.mozilla.org/en-US/kb/search-engine-removal?as=u&utm_source=inproduct
twitter.com/NSFWRedditVideo

works on my machine

Attached: works on my machine.png (200x193, 52.58K)

I thought Firefox was open-source? Why no one fixed these decade old issues yet?
... Was FOSS a lie all along!?

Attached: uuvZuoMM-IY.jpg (50x50, 2.36K)

Just works for me Chromium is more buggy especially on Wayland the architecture is more worse than Firefox while not perfect

>>Doesn't support HDR on sites like YouTube.
>- Why is Firefox unable to correctly view content on the #1 video site in the world?
fucking retard, Google intentionally breaks working features on Firefox to stifle competition. They're fucking cunts. Why would you help them? They are shitting in your mouth and telling you to use their browser while they cum in your ass. You are literally letting some fuck shitting in your mouth cum in your ass as a reward for not shitting in your ass anymore.
The rest of your post also gives the impression that you're just shitting on it for fun, likely getting paid. I have zero, ZERO issues with Firefox for years. No lag, no crashes, nothing.

Current browsers code base are so big no one wanna lose their sanity with them, same feeling as developing for a OS without the glory of developing for Linux Kernel i.e, don't take me seriously tho, this is not something I've read it's just out of my ass opinion

Works just fine on my machine
>Doesn't play nice with Enterprise deployment and configuration management.
github.com/mozilla/policy-templates
>>Doesn't pick up the operating system PKI trust store.
Add ImportEnterpriseRoots to your group policies

>likely getting paid
At least that's better than you sucking trannyzilla dick >for free.

Yup, classic paid shill behavior. Spam trannyfox 24/7 thinking it's a good argument while Manifest V3 creeps up.

Chrome follows w3c as well as Firefox. Accept it, your browser sucks.

It's simply reality that Firefox is in the gutter and Mozilla refuses to get their shit together. That Any Forums screams nothing but "Manifest v3! Manifest v3! Manifest v3!" is testament to the fact that Firefox falls behind chromium browsers in every other aspect.

t. someone who switched over to FF precisely because of Manifest V3.

>Chrome follows w3c
AHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA
theregister.com/2021/10/04/chrome_breaks_web/
^fuck standards
>"Chrome is deprecating the blocking capabilities of the webRequest API in Manifest V3, not the entire webRequest API (though blocking will still be available to enterprise deployments)," wrote Vincent in a Chromium forum post on May 24.
>And in a statement, Google said it "supports the use and development of ad blockers." >The company is working with developers to create a "privacy-preserving content filtering system that limits the amount of sensitive browser data shared with third parties." It didn't comment in detail, though.
^fuck adblocks
I mean really, an ad company fucking with adblockers, who is surpised they don't care about anything.
Whenever there is something they don't like, they'll just break it and expect everyone to bend over. Whenever there is something they want they'll just implement it without caring about any standards and then say "look at this other browser that doesn't support our new feature already, it sucks! bad browser!" and force other browsers to implement everything they invent by pushing google services to be "worse" on other browsers because they intentionally crippled it.

Firefox is just fine. Literally NEVER had an issue. No lag. No crashes. No bugs.
People like to scream and cry about how it's not chrome, but they're just whining toddlers refusing to get used to it or configure it to be more similar to the browser they used to have to ease the transition.

>>Doesn't consistently support colour management.
>>Doesn't support HDR on sites like YouTube.
>>Doesn't pick up the operating system PKI trust store.
>>Doesn't play nice with Enterprise deployment and configuration management.

>firefox doesn't support memes and useless technology

k nigger
i'm the first to criticize foss software when it's bad (like lin*x) but i've been using firefox for years and i never had a problem. and yes i use chrome or opera every once in a while too

this. OP is just inventing problems. FF just werks. as long as i am not getting immediately hacked after opening a porn site, i am good.

No it's because Firefox keeps adding bullshit "features" nobody asked for instead of fixing decade-old bugs. Who wanted the all the crap they recently added to the address bar drop-down? No one. Furthermore they force you to dig into about:config entries intentionally obfuscated from the end-user to disable this kind of crap. Just an hour ago FF deleted all my search engines and showed me this support.mozilla.org/en-US/kb/search-engine-removal?as=u&utm_source=inproduct despite me being on the latest version.

Quit blaming users for Mozilla's fuck-ups.

>these features don't matter, because I don't use them
kys

Dishonest shill.

>Quit blaming users for fuck-ups
you're asking to get rid of the very essence of open source software
those features don't matter bc no one uses them or even know they exist
if you have a niche use case obviously many of the generally used options will not work for you. that happens with any kind of software. just use chrome and stfu

>every day new browser shill thread
i'll keep using icecat

Pissy fanboy who can't accept legitimate criticism. Apologists like you just further enables the Mozilla's executive's retardation and will be the cause of Firefox becoming totally obsolete.

Notice the word "roots" in "security.enterprise_roots.enabled"?

The PKI hierarchy is more than just "roots". A tree is more than just a stump. As a random example of how this can be broken in Firefox is that it is unable to use LDAP to load an intermediate CA certificate. The use of LDAP is common on large Windows-based enterprise networks, because it's the default. It's trivial to "push" these intermediate CA certs into the local trust store of every machine using policy, at which point the protocol support no longer matters. Firefox could have simply picked up the certificate from the local store. It already has the code for doing this for Root certs, but refuses to use identical code for Intermediate certs.

No amount of begging or pleading with the Mozilla dev team ever succeeded in convincing them to read the Microsoft documentation for how PKI works in Windows.

There's a set of constants in the Win32 headers that defines the various certificate trust stores in Windows. You know, "machine", "machine policy", "user", and "user policy" multiplied out to make combinations with "root", "intermediate", "crl", etc...

Over 20 years they have slowly, one at a time added a random subset of them. RANDOM. Just... one... at... a time... in some unfathomable order. It was mind-blowing to watch this unfold.

The simplest thing they could have done was simply support all of the stores by copy-pasting the whole block of constants and writing a for loop across all of them. Done. Fixed. Close ticket.

But noooo... got to keep those tickets open for decades and decades by making sure that whatever is there remains permanently incomplete.

>>>Doesn't consistently support colour management.
>>Doesn't support HDR on sites like YouTube.
>>Doesn't pick up the operating system PKI trust store.
>>Doesn't play nice with Enterprise deployment and configuration management.
meme shit and enterprise shit (why do you even care about that?)

Why do you even care?