How about no?

Everything worked perfectly as it always does.

You're viewing a single thread.

142 comments

Classy to blame Firefox for bugs in their code :)
If devs write code for Chrome, yeah, maybe then it doesn't work in Firefox guys....
We had exactly this situation in the 90s with internet Explorer.... But new devs need to relearn lessons of course.
- It was different in the case of IE though. It was actually atrocious and not standards compliant in many many ways.
  Today, chrome and FF both support standards fairly well and when things don't work in FF it's usually either that you wrote fragile code, or there's a slight difference from chrome that technically isn't a standards compliance issue. Testing in both of those browsers isn't hard and should be the norm. I've had projects where I had to test in IE, chrome windows, chrome android, FF, safari Mac, safari iPad OS, and safari iOS all at the same time. And yes there are differences between those last two, because apple makes a shitty web browser.
  If you can't test in two browsers, you're just a bad web developer...
  
  Absolutely this, nothing but pure laziness. I had a really weird specific issue on iOS Safari with one of my projects, and I own literally nothing Apple. Instead of just accepting shits fucked on iOS, I got my hands on a borrowed Mac so I could use xCode and actually find the issue.
  ...then again, that project ended up dead in the water at like 95% completion and I never got paid for the work I'd already finished, so maybe the joke IS on me and I should've been a lazy fuck.
  
  Sounds like you might want to add some sort of terms of agreement to your estimates. I built sites that never saw the light of day, but that is entirely up to the client. A site not being live doesn’t mean my client doesn’t need to pay me.
  
  It was for a family friend who is disabled and unable to work a normal job, so me and my brother(also a dev on this) agreed to be paid on project completion. Long story short, she wasn't able to pay so the final bug fixes were never done, and the code has been left to rot. Under different circumstances I'd be putting pressure to get at least some payment, but it's pointless imo.
  Lesson learned though, not doing that again.
- It could be they were using new features chrome added which Firefox had as experimental when they wrote it. Firefox recently promoted those features to stable.
  
  It could be but then it's even worse judgement. They basically don't care if Firefox users can view their web site, and that's one thing, but blaming it on Firefox is kind of rich, instead of taking responsibility for their decision. :)
- It's probably all the new generation of programmers/management - you would think they would listen to the lessons passed down but.... Nope.
  
  Depressingly, the message that GHG emissions are heating up the planet has been passed down for over a hundred years now. People just aren't very good with passed down messages in general.
  
  See also: measles vaccinations.
  
  You're assuming that lessons are being passed down.

142 comments