Here is an example of Google’s homepage not rendering correctly in Chrome:<p><a href="https://twitter.com/sroussey/status/1273341472398381056?s=21" rel="nofollow">https://twitter.com/sroussey/status/1273341472398381056?s=21</a><p>Really, if they have these kinds of problems, then the rest of us... :/
The compatible problem is Microsoft and Safari, not Chromium
and Firefox. I run a web development agency, and supporting the limitations IE has always been a significant cost and challenge. As the joke goes, "What is the definition of HTML5? If it works in IE, it's not HTML5".<p>I have mixed feelings about Microsoft giving up on their browser. On the one hand, it will make things more compatible and reduce effort for us. On the other, it's one step closer to a monoculture controlled by Google. I would prefer that Microsoft simply get their shit together and make a good browser.
I’m glad to see some traction, finally, for improving <input> elements. They’re the source of my current pains:<p>* Still no real combobox. <datalist> is only a half-way solution.<p>* <optgroup> should be nestable - rarely do things fit into only 2 levels of depth.<p>* Biggest pain of all: Radio-button events.
I hope they fix chromium's weird subpixel bugs like this one: <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=717469#c_ts1513250807" rel="nofollow">https://bugs.chromium.org/p/chromium/issues/detail?id=717469...</a>