News for hackers. Stuff that matters.
Re:Firefox 49 fixes sites designed with WebKit in mind, and ... by masklinn on Wednesday September 21, 2016 @04:01AM (#12546243)
> If firefox doesn't support -webkit prefix, the developers are forced to consider the compatibility issues

Evidence shows that they don't, and that developers are absolutely not going back and fixing code they shipped years ago, so all the principled stance nets firefox is "firefox breaks <outlook mobile>, it works just fine in chrome, screw that piece of shit firefox".

Re:Firefox 49 fixes sites designed with WebKit in mind, and ... by pmontra on Wednesday September 21, 2016 @07:57AM (#12547319)
Developers would, but do their customers pay them for that? Evidence is that they don't.
Re:Firefox 49 fixes sites designed with WebKit in mind, and ... by StillBored on Wednesday September 21, 2016 @12:46PM (#12549909)
Blah, my $%#$% credit union, upgraded their web software the other day, and it basically supports only the latest FF, and chrome browsers on the desktop. Complete with a nice please download chrome button, and a refusal to proceeded. I'm running a webkit based alternative browser, and I had to go change my compatibility string to get past it.

I opened a ranty support request about the fact that they should consider replacing their web devs if they were unable to create a site that adhered to standards enough that they didn't feel the need to write browser specific code.

Having spent some time in the past few years doing web development myself, I don't feel the least bit sorry for web developers that are using browser specific prefixes, or other crap. In my experience its actually chrome that has serious rendering bugs these days, and FF/IE manage to render pages pretty similarly. So, at this point if your a web developer using chrome as your default target, that should be considered incompetence.