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