I've seen that one as well (and tagged a rendering lead on Chrome on Twitter just now). Thankfully it's a painting artifact and not a layout/behavior issue, likely because the invalidations are not accounting for the way shadows expand the layer bounds in some situations.
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".
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.
> And not all browsers support basic features like Datepickers etc. (I'm looking at you Safari)
This is a real pet peeve of mine. Perhaps there is some good reason, but as far as I can tell date pickers work well in chrome and firefox, and not having one in safari means you need to add javascript to your page and/or do some nasty server side user agent sniffing stuff to try and make sense of dates.
It's somewhat ironic (moronic?) that Apple was the first to add support for `<input type="date" />` in Mobile Safari for the iPhone almost a decade ago - so it's a complete mystery why macOS Safari doesn't have this feature.
Here's Apple's Radar entry: rdar://problem/14567780 (I don't have access to Radar - can someone who does please let us know what the latest update is?)
Right now we use a quick-and-dirty date polyfill for macOS Safari - though more recently our GA stats show that 90% of our macOS users are using Chrome anyway which supports date inputs natively so for our lesser-used pages and areas I might forget to add the polyfill and we won't hear any complaints.
Thinking about it more - I noticed the WebKit Bugzilla ticket mentions a problem with integrating Qt's date-picker for other Webkit platforms - and I noticed that Apple's date-picker in Cocoa is a bit... old-fashioned, I wonder if Apple's just dragging their feet until they modernize their date-picker in macOS?
It's kinda mean to do that though - if that is the case then they're deliberately holding back the web, increasing web-development time, and worsening accessibility (so many inaccessible JavaScript date-picker components!) just so that they can avoid "looking bad".
> It's kinda mean to do that though - if that is the case then they're deliberately holding back the web
Kind of like the way they refuse to support open formats like WebGL2, glTF, webP, various compressed GPU texture formats and probably lots more I'm not aware of.
Apple devs always answer "we're working on it" when pressed on these issues. But after several years of seeing the same half-hearted answers these assurances start to ring hollow.
We expect it'll be ready for testing in a few months. However we expect that it'll be a bumpy rolling this out as table layout has a long history, and isn't exactly well defined :).
It's probably because web devs have experienced years of pain due to MS holding back the web platform. They've made some positive changes recently but it'll take them a lot more to atone for past mistakes.
https://twitter.com/sroussey/status/1273341472398381056?s=21
Really, if they have these kinds of problems, then the rest of us... :/