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".
8 comments
[ 3.2 ms ] story [ 15.3 ms ] threadGiven the introduction of the spec is about correctness I… guess that means they already implemented whatever the site checks for correctly?
<tr id="enabled" style="position: sticky; top: 1px; left: 0;"><th>YES</th></tr> <tr><td id="notenabled">NO</td></tr>
should just say if you still have the Chrome table rendering bugs or not.
> 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".
Yeah, sounds really critical for that extra slight degree of issue detection.