Be aware of Chrome's new table layout engine

tablesng.com

11 points·duncans··8 comments

Note the comments on some of these bug fixes:

> Interoperability: matches Firefox.

This is why it is so critical to have multiple browsers with independent engines.

Apparently Firefox was adhering to the standards correctly and Chrome now matches this output.

If there was no Firefox, would anyone care? It may have been caught but not as easily as if users are complaining that a site "doesn't look right in Chrome, but looks fine in Firefox".

> This is why it is so critical... It may have been caught but not as easily...

Yeah, sounds really critical for that extra slight degree of issue detection.

This is a better URL: https://docs.google.com/document/d/16PFD1GtMI9Zgwu0jtPaKZJ75...

According to the check this site does, apparently Firefox has Chrome's new table layout engine

As does Safari.

So does Safari on iOS.

Given the introduction of the spec is about correctness I… guess that means they already implemented whatever the site checks for correctly?

There's no JavaScript on that page so I guess the HTML used as the test

should just say if you still have the Chrome table rendering bugs or not.

On my Mac, Chrome says NO, while Safari says YES. Which seems odd, given the complaints about Safari's implementation of tables on the linked page.

Reply on news.ycombinator.com