We Need Chrome No More

Re:We Need Chrome No More by fastball on Wednesday February 27, 2019 @12:20PM (#19264874)

And if you build to the standards, it's possible that no actual browser implements them correctly.

And then what?

[ Parent | on HN ]

Re:We Need Chrome No More by CharlesColeman on Wednesday February 27, 2019 @01:26PM (#19265612)

> And if you build to the standards, it's possible that no actual browser implements them correctly.

> And then what?

Build to standards first, then accommodate quirks last.

Building to Chrome first is just building to its quirks, and totally forgetting about standards.

[ Parent | on HN ]

Re:We Need Chrome No More by Zarel on Wednesday February 27, 2019 @01:31PM (#19265653)

I'm not sure what the difference is. It's not like people learn HTML from Chrome's source code. They learn HTML from places like MDN, which document web standards.

"Write HTML, test on Chrome" - what people do in practice - seems to fit "build to standards first, accommodate quirks last" just as well as "build to Chrome first".

[ Parent | on HN ]

Re:We Need Chrome No More by saagarjha on Wednesday February 27, 2019 @12:28PM (#19264971)

You wait for them to do so, and are vocal whenever this happens.

[ Parent | on HN ]

Re:We Need Chrome No More by fixermark on Wednesday February 27, 2019 @12:41PM (#19265118)

"Wait for them to do so" is an answer that guarantees your team will get passed over in favor of a team that brought a working product to market today, to solve real problems real users have.

[ Parent | on HN ]