Yes, that's the point of having a set of standards. Otherwise you end up with an...

dylan604 · on May 21, 2019

Otherwise 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 · on May 21, 2019

Chrome is based on Webkit which is free and open source so that is a terrible analogy with IE that was proprietary.

mathieuh · on May 21, 2019

Its being open source isn’t mutually exclusive with its not adhering to the standard

judge2020 · on May 21, 2019

Chrome 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 · on May 22, 2019

Blink is also under a FOSS license so I am not sure what the problem is. Competiting browsers use Blink as well.

jwandborg · on May 21, 2019

If it was that simple there would be no reason for Safari to lag behind.

sureaboutthis · on May 21, 2019

No 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 · on May 21, 2019

I 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.