4 ms·
Make no mistake, it's still a dumpster fire. Just maybe less raging.
by datalus 6y ago
Make no mistake, it's still a dumpster fire. Just maybe less raging.
- brundolf 6y agoI worked on a highly complex web app for ~3 years, and we made a point to support Firefox, so whenever somebody had a Firefox-specific bug we wouldn't tell them to just use Chrome, we'd fix it. We only had 2-3 Firefox-specific issues in that entire time. I have heard that mobile safari can be a bit more unruly than the rest, though it isn't really relevant to the question at hand
- mrec 6y agoSimilar. Built a very complex app officially aimed at oldIE but made a point of ensuring it worked on other browsers too, largely on a skunkworks basis. A few years later (when we're no longer actively working on the app) everyone switched to Chrome and it Just Worked. Someone tried it on an iPad and it Just Worked (modulo some fat-finger challenges with small UI affordances). At the time, jQuery was a big help in this, especially in hiding the event model mess. Things are a lot better now. Although I do wish we had a strict compatibility-checking layer that'd warn you if you used any feature of the web platform that wasn't supported by everything you wanted to support.