61–65 of 65 posts
Earlier quoted context omitted.
Chrome does not support ? Interesting.
Chrome supports . cowboyhero was making an allusion to the browser wars[1]. [1] https://secure.wikimedia.org/wikipedia/en/wiki/Browser_wars#...
Earlier quoted context omitted.
Have they acknowledged the bug and refused to fix it?
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.
Eh. They did a vanity site to promote a product. When Goog starts adding /marquee/ tags and VBScript to their browser, I'll start getting worried about "openness."
It is clear to me that this is a Google Chrome Experiment, from their labs, and that they did not had any intention of it working on any other browser but i got curious... i was doing some research on it and they appear to be using sync xhr calls which causes FF to hiccup even after all this time. https://bugzilla.mozilla.org/show_bug.cgi?id=383304 https://bugzilla.mozilla.org/show_bug.cgi?id=313646 they are marked a…
Er... there is no synchronous XHR in the snippet you pasted. All calls to open() pass true for the third parameter.
It is clear to me that this is a Google Chrome Experiment, from their labs, and that they did not had any intention of it working on any other browser but i got curious... i was doing some research on it and they appear to be using sync xhr calls which causes FF to hiccup even after all this time. https://bugzilla.mozilla.org/show_bug.cgi?id=383304 https://bugzilla.mozilla.org/show_bug.cgi?id=313646 they are marked a…
Huh? Where do you see a sync XHR in there?