Fuck Mozilla! !!
Why do yu mess everything up
My app looks nice and neat in Chrome
Load up Firefox and the whole thing crumbles

*sigh*

Internet Explorer: Try it on me

It seems to me that Google sometimes implements stuff which is according to Google standards but not according to the general W3C standards and when developers follow the Google standards...

Not sure if this is the case here but for example Twitter had a bug recently where sensitive content was stored in cache but they were only developing on Chrome and this seemed to be a "Google standard" so other browsers stored this differently than Chrome.

I could also be wrong of course but I develop front end in Firefox only and I never come across such issues! (my friends who develop in Chrome/Chromium do on non-Chromium browsers)

Chrome isn't standard. I think this might be intentiomal, a smart way to make every other browser seem buggy and noncompliant, since Chrome _is_ the majority.

I recommend developing in firefox in the first place, their flex and grid tools are quite nice.

@theuser

This

Thank you all
I thought Mozilla was the culprit
[Sorry Mozilla devs if any of y'all here]

Also I am running test on Kali VM using localhost and its slow to load up

Is there anything I can do to speed it up

@Taqsblaz3 what do you mean with "load up"?

Missing -moz prefixes I guess

@kamen If u are using prefixes, you should expect different behaviour. If you set prefixes manual... Hell awaits.

@linuxxx Google is one of the main contributors when it comes to web standards, so they often don't wait for things to get standardised before coming up with initial implementation. I'm not aware of "own standards", everything in stable releases seems to be backed up by w3c.

9/10 times I found something behaving differently in FF, I found a corresponding issue on Bugzilla. There's not an insignificant amount of issues, most of them already a couple years old, regarding FF implementation differing from standards (try searching w3c on bugzilla for start). Before Chromium-based Edge, I'd even find thins to work in Edge but not in FF, and of course, there was always a really old issue regarding that use case, waiting for someone to "feel like fixing it" on bugzilla.

@hitko For the record, this is something I read about multiple times, I haven't experienced it much since I'm mainly a backender, Linuxer and cyber security guy and only use Chromium when really necessary.

One thing that is very apparent, though, is how Google sometimes "sabotages" their own products to only work properly in Chromium based browsers and more stuff like this. But that's for another rant!

@IntrusionCM
Like if I click on a link the page takes time to load

@kamen
Yes but doing that manually
I'll have to declare an attribute twice because just one with
-moz won't work on chrome

More like:

I learned to code on YouTube

@Linux lol
I literally graduated from YouTube collage
then graduated from the University of Google
all from the comfort of my bed

@linuxxx I've heard about one report that "Former Microsoft intern claims Google may have sabotaged Edge browser" - there's been a lot of debate following, but most remained sceptical, as the evidence is anything but clear.

The other related issue I can think of is how YouTube became really slow in FF after the Polymer rewrite, and I know the community blamed that on Google - however as far as I'm concerned that one's been entirely Mozilla's fault. At the time (late 2017) it's been more than 6 years since web components v0 proposal, more than a year since v1 has been standardised, and FF still didn't have even experimental support for these features - what's been slowing it down wasn't something Google did with YouTube, but actually their own lack of support for new standards, which required use of a rather big polyfill.

@hitko Yeah that kinda stuff. This is one of the only reasons I keep Chromium around.

I hardly use Google products but YouTube regularly randomly doesn't work for me on Firefox and the captcha's can take 10+ minutes on Firefox with clicking myself to death and on Chromium they magically always work right away.

@Taqsblaz3 Yeah but on Firefox not putting in the moz- prefix still works fine... (source: me right now)

@linuxxx
Hahaha... owky well on my side it failed like crazy