4 ms·
Doesn't work in Google Chrome for some reason. You just get a simplified version (no sparkly goodness). Anyone care to speculate why Apple made this decision, g
by brianwillis 16y ago
Doesn't work in Google Chrome for some reason. You just get a simplified version (no sparkly goodness). Anyone care to speculate why Apple made this decision, given that Safari and Chrome are both webkit based?
- jonursenbach 16y agoI see it just fine in 7.0.517.44.
- pyre 16y agoI'm in Chromium 9.0.576.0 and it doesn't seem to work for me.
- confuzatron 16y agoI'm getting no animations in 7.0.517.44.
- elliottcarlson 16y agoSame here - displays fine in 7.0.517.44 - not sure if I think this is all that "badass" though...
- jjcm 16y ago(All browsers are tested in Ubuntu 10.10 unless otherwise mentioned) Chrome 8.0.552.11 dev - works Chromium 7.0.517.44 (64615) - works Firefox 3.6.12 - Shows a "browser not supported" page, clicking through makes it work just fine. Did notice though that the animation only happens when the window has focus - probably a nice addition so it doesn't chomp CPU time in the background. Firefox 4.0b8pre - Fails. Blank screen. Opera 10.60 (6344) - "Browser not supported" page. Animations do not work, logo doesn't render. Seems to fail gracefully (login fields still accessible). IE6 (windows xp) - Fails. Does not degrade gracefully. IE 7.0.5730.13 (windows xp) - Different warning page than FF/Opera. Degrades gracefully, no animation. So far seems to be pretty focused on webkit browsers. No huge surprise there. What was interesting was that IE6 wasn't supported at all. There isn't even any "continue anyway" button after the "browser not supported" page.
- archangel_one 16y agoWorks okay for me at first in Firefox 4.0b7 - but after a few seconds of playing with the sparkles following my mouse (nearly as childish as it sounds) it abruptly stops and they vanish. No JS error reported.
- brianwillis 16y agoInteresting. I deleted my cookies and saved passwords and it displays correctly.
- dtwwtd 16y agoI'd assume it's because Safari's JS interpreter (Nitro) is a different interpreter than Chrome's V8