5 ms·
Yes, that's the point of having a set of standards. Otherwise you end up with an IE situation where everyone just develops for a single browser.
by jpat1 7y ago
Yes, that's the point of having a set of standards. Otherwise you end up with an IE situation where everyone just develops for a single browser.
- dylan604 7y agoOtherwise you end up with a Chrome situation where everyone just develops for a single browser. You're commented needed to modified for current times. ;-)
- ekianjo 7y agoChrome is based on Webkit which is free and open source so that is a terrible analogy with IE that was proprietary.
- mathieuh 7y agoIts being open source isn’t mutually exclusive with its not adhering to the standard
- judge2020 7y agoChrome uses its own Blink and V8 now, and there are many cases where developers only design for Chrome and small differences in implementation can be a huge pain in Firefox/Safari.
- ekianjo 7y agoBlink is also under a FOSS license so I am not sure what the problem is. Competiting browsers use Blink as well.
- jwandborg 7y agoIf it was that simple there would be no reason for Safari to lag behind.
- sureaboutthis 7y agoNo professional developer targets a browser when developing a web site unless its a captured audience with no choice. Professional developers follow the specification. Those who do otherwise are only mentioned in reddit headlines and other hobbyist sites.
- JMTQp8lwXL 7y agoI understand that's the intent of standards, but rarely are there not limitations or bugs in implementations. If this was truly the case, we wouldn't need things like Applitools to view our HTML documents in various browsers to scan for differences.