4 ms·
I'm pretty sure this is a commentary on the laziness of devs/why browser dominance is bad for standards, when taken in context: > The dominance of Chrome has a
by guitarbill 8y ago
I'm pretty sure this is a commentary on the laziness of devs/why browser dominance is bad for standards, when taken in context:
> The dominance of Chrome has a major detrimental effect on the Web as an open platform: developers are increasingly shunning other browsers in their testing and bug-fixing routines. If it works as intended on Chrome, it’s ready to ship.
When you're following decently established standards (not bleeding edge), it's usually Chrome that breaks now, not Firefox or Safari. Chrome truly is the new IE.
- fixermark 8y agoI haven't personally encountered this phenomenon. Can you give an example of an established standard that breaks on Chrome but FF / Safari handle?
- guitarbill 8y agoIndeed I can, although one anecdote does not data make. The latest was using SVG sprites as background in CSS I think. Maybe I can throw up a demo during my lunch break, but honestly it isn't that exciting. It just doesn't work correctly in Chrome, the sprite is cropped/has a weird rendering artifact.