Since most proprietary web applications fail to work properly in Firefox, it makes sense that FOSS web applications should be primarily developed using Firefox.
yeah, if they cut the interoperability out, the opposite side should do the same
They want a war ? They'll get it
Here's full-time FF user and full-time web developer. FF is barely keeping up with devtools. Everything but the basic CSS is pain. At least they improved sourcemaps recently, was unusable before that.
I do my web dev in Safari, which has the best console and tends not to ship bleeding-edge features before they work. Sometimes I remember to test before release on Chrome, Firefox, & Edge. FF's always the slowest and most broken of them.
@charlag @njoseph_1 "You're holding it wrong". Almost by definition, if WebKit does it, it's "right" and everyone else is wrong. And some of that trickles half-assed into Chrome after they figure out how to break it so Google can sell more ads, and then Firefox months or years later reads the spec and quarter-asses it.
The Safari console debugger's been there for over a decade, it's essentially the same as Xcode's.
@charlag @njoseph_1 Shrug. File a bug. With IndexedDB, it's more likely you're hitting storage capacity, Safari severely restricts it and prompts the user even before that cap. Which is why I've gone entirely to electron, or storing stuff on server, or back to native code. Web storage enables ad tracking.
I doubt CSS is doing "random shit", and if you look in the Safari inspector, right-side bar shows CSS hierarchy for any element. So far I've always found that I'm the bug in my CSS.