4 ms·

I remember fixing one of frontend bugs in an SPA and contrary to the claims it turned out to be a webkit bug that the code relied on (the app had been developed

by emn13 11y ago

I remember fixing one of frontend bugs in an SPA and contrary to the claims it turned out to be a webkit bug that the code relied on (the app had been developed on a mac, so it's fairly easy to only test on webkit/blink). Lovely. Aside/Rant: I also get the impression that frontend devs have never read the CSS2.1 spec or bothered to understand it (CSS3 is longer, and consists largely of special-purpose extra modules, so a complete reading is less valuable and more difficult). There's somehow this feeling that since CSS "isn't a real programming language" you should be able to use it intuitively. And when things don't work out and you fiddle until it works without giving thought to why, that's OK. That's such a huge waste of time. The box model may not be 100% intuitive, but boy, if that's your standard, what you doing in IT?

masklinn 11y ago
> the app had been developed on a mac, so it's fairly easy to only test on webkit/blink It's no harder to only test on Chrome in Linux and IE in Windows, I fail to see how that's an excuse. The only excuses are IE testing when developing on OSX and Safari testing when developing on Windows, it's trivial to install both Firefox and Chrome on any OS.
- emn13 11y ago
  Actually, it's easier to test for IE versions on linux/mac due to http://xdissent.github.io/ievms/ http://xdissent.github.io/ievms/ - You can install the VMs on windows too (of course), but I've never stumbled upon quite as simple a solution. On windows I tend to just rely on compat mode, which is surprisingly good, but far from perfect.