Re:Google's playing the closed-open game again, this time wi...
by icebraining on Wednesday July 27, 2011 @02:40PM
(#2813478)
Have they acknowledged the bug and refused to fix it?
[ Parent
| on HN ]
Re:Google's playing the closed-open game again, this time wi...
by ZoFreX on Wednesday July 27, 2011 @04:43PM
(#2814010)
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!
Re:Google's playing the closed-open game again, this time wi...
by jmesserly on Wednesday July 27, 2011 @04:00PM
(#2813849)
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.
Re:Google's playing the closed-open game again, this time wi...
by bzbarsky on Thursday July 28, 2011 @02:43AM
(#2815676)
> 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.