3 ms·
Firefox manages to do decent but the point is that just because a browser is standards compliant doesn't mean websites will look good in it if everyone is only
by zamadatix 7y ago
Firefox manages to do decent but the point is that just because a browser is standards compliant doesn't mean websites will look good in it if everyone is only developing for Chrome. It's not that Edge or Firefox are bad.
- wnevets 7y agoMaybe but that was a terrible example IMO. It was purposefully built to work with chrome
- zamadatix 7y agoIt's not that it was made to work only in Chrome - it was only tested in Chrome. Whether or not it worked in other browsers didn't matter. That's EXACTLY what I'm trying to point out, it's not a bad example it's literally the example that made me comment in the first place. The other browsers are very standards compliant, doesn't matter - still broke.
- wnevets 7y ago>The other browsers are very standards compliant, doesn't matter - still broke. because it wasn't made to be standards compliant. It's just an art project someone threw together in 2 hours, not an actual website.
- zamadatix 7y agoThe problem being highlighted is precisely that sites are no longer being made to be standards compliant they are being made to work with Chrome. It's not a question of WHY it doesn't work in other browsers or WHY it was made that way, it's just that things aren't made based on being standards compliant anymore. Also I recommend checking out the post/page if you think it was just a 2 hour pump and dump css show off. It's multiple pieces made by handwritten LESS on the order of 4,000 lines over hundreds of commits per drawing.