Have they acknowledged the bug and refused to fix it?

ZoFreX · on July 27, 2011

One of them is already getting attention so hopefully they will notice (you know how it is), the other one has literally only affected me as far as I can see and I haven't put together a minimal test case yet. It's a weird one!

jmesserly · on July 27, 2011

Agreed, it would be nice to see the bug. AFAIK they take standards compliance pretty seriously. I'm sure someone would look at it, especially if Chrome is behaving differently from FF/IE9/Safari.

bzbarsky · on July 28, 2011

> AFAIK they take standards compliance pretty seriously.

As long as it doesn't interfere with their performance benchmarks.

http://weblogs.mozillazine.org/bz/archives/020267.html is an example; that issue is alive and well in WebKit, as are various other "optimizations" along similar lines.