Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Improving Chromium's browser compatibility in 2020

blog.chromium.org

Post reply on HN
Print view View original

1–10 of 20 posts

Re: Improving Chromium's browser compatibility in 2020

#5

Post by DaiPlusPlus »

I’m glad to see some traction, finally, for improving elements. They’re the source of my current pains:

* Still no real combobox. is only a half-way solution.

* should be nestable - rarely do things fit into only 2 levels of depth.

* Biggest pain of all: Radio-button events.

Re: Improving Chromium's browser compatibility in 2020

#6

Post by esprehn »

sroussey wrote: post #3

Here is an example of Google’s homepage not rendering correctly in Chrome: https://twitter.com/sroussey/status/1273341472398381056?s=21 Really, if they have these kinds of problems, then the rest of us... :/

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.

When finding things like this file bugs at https://crbug.com/new

Re: Improving Chromium's browser compatibility in 2020

#8

Post by bfgeek »

polskibus wrote: post #7

I hope they fix chromium's weird subpixel bugs like this one: https://bugs.chromium.org/p/chromium/issues/detail?id=717469...

We are in the process of revamping our table layout code at the moment - this should remove subpixel issues like this. Our master bug for these subpixel issues is: https://bugs.chromium.org/p/chromium/issues/detail?id=377847

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 :).

- Ian

Re: Improving Chromium's browser compatibility in 2020

#9

Post by djxfade »

DaiPlusPlus wrote: post #5

I’m glad to see some traction, finally, for improving elements. They’re the source of my current pains: * Still no real combobox. is only a half-way solution. * should be nestable - rarely do things fit into only 2 levels of depth. * Biggest pain of all: Radio-button events.

And not all browsers support basic features like Datepickers etc. (I'm looking at you Safari)
Post reply on HN