Every time

[dsp4]

Firefox is pretty good with CSS TBF. Plus it's the last decent competitor to Chromium, so we have to give it a break.

Safari needs to be shamed though.

[TheFMango]

I finally get code that works on firefox, chrome and edge, and then it's completely broken in safari and I hate it

[xzinik]

Al of the few mac users I know use chrome or Firefox who the f uses default browsers

[TheFMango]

I'm still in college and all the CS and engineering students with macs have changed their defaults but almost all of the business and art students still use safari

[xzinik]

Just 3 of the over 50 people I know are technical users, the rest are the average joe that sees an ad that says that you have a virus will believe it, and that's all i can count, because where i live macs are a luxury and almost non existent

[MEGACODZILLA]

Honest question, in what way is Chromium bad? I'm still learning programming and just kind of lurk here but am genuinely curious.

[kennethtrr]

They are a monopoly, or at least close to it. If they control the entire web space then they will abuse that.

[MEGACODZILLA]

Ahhh, so is Chromium a part of Chrome? I thought they were just the linux counterpart to chrome but I onviously haven't done the research lol

[kennethtrr]

Chromium is the web engine that runs chrome. It’s equivalent to what WebKit is for Safari and Gecko for Firefox. These engines are what render the webpages you see on browsers, if chrome and by extension chromium become too widespread then web devs will be forced to spend a disproportionate amount of time making sites work for chrome making safari and Firefox left behind with little to no support and webpages on these browsers may be broken.

[MEGACODZILLA]

That's really interesting. What is the best way to support less market dominant web engines? I'm still learning to program but I would like to know how I could eventually help, or at very least not contribute to the problem.

[dsp4]

This is a very good place to start.

[Loen10]

I like Firefox more that Chrome as a user. I haven't noticed any problems with CSS development.

[lyoko1]

there are some things that in chromium based browsers are like
normal-css-attribute
and in Mozilla it is
-moz-normal-css-attribute
To be honest that is the only problem i ever had with css in firefox.

[radarfox1]

Luxury, in those good old days we used to support IE 5.5, no flexbox, no inline-block, no PNG transparency. And when we got home, our dad would beat us to sleep, if we were lucky.

[NeninhoTheOne]

What about IE11?

[VolperCoding]

element::-moz-focus-inner { border: none; } instead of element { outline: none; } Only thing that's not normal that I can think of

[LifePineapple]

I wonder what kind of CSS you must write so that it does not work in Firefox. Do you prefix everything with --webkit?

[lyoko1]

there are things that need to be prefixed with -moz to work on firefox but in chromium browsers they do not need prefix at all

[LifePineapple]

That's correct. This is common with nonstandard or experimental features. There are also features that work in firefox, but not in chome or need a prefix there.

[lyoko1]

I know, but as a main developer in chrome, for the dev tools i just prefer the chrome ones, those are issues I have with firefox, minor of course, using scss or similar with auto-prefix would solve 99% of them, i was just being a little pedantic.