Summary: | REGRESSION; background-image javascript rotation fails after initial load | ||
---|---|---|---|
Product: | WebKit | Reporter: | nemo <bugs> |
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Major | ||
Priority: | P1 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Other | ||
OS: | All | ||
URL: | http://epss.ahrq.gov |
Description
nemo
2008-09-24 09:10:16 PDT
Oh. And althought the images worked normally after the mentioned hitting of reload, even after restarting browser, if I cleared cache, the bug reproduced itself repeatedly. <script type="text/ecmascript"> window.onload = function() { var i = Math.ceil(Math.random()*3); var m = document.getElementById("main"); m.style.backgroundImage = "url(images/front_background"+i+".jpeg)"; // can tweak size as needed. images are mismatched /*if (i==1) m.style.height = "360px";*/ } </script> is what loads the background images. Works fine for me on the mac. I even cleared my cache to verify. I guess someone could check on windows, but I expect this is not a bug. Well. Let me retest on windows with latest build. I know what was causing the background to load, the odd thing was that it would stop working. That was the bug bit, and was only reproducible in the windows nightly I was using, not in Safari, Firefox nightly or Internet Explorer. Soo, it might be "fixed" But at least in r36766 it was definitely a bug :-p Still able to reproduce, in a completely different windows XP (virtualbox this time) using the nightly build from the 25th, r36882. Will test under OSX to see if I can expand the platform - it might be Eric wasn't following my test instructions. :) Reproduced in nightly for the 29th, r37056 under OSX so I'm expanding platform. I'm at a loss as to comment #2 from Eric. The behaviour in WebKit is definitely buggy. Safari, Firefox, Chrome, and even IE all have no trouble displaying all 3 of the background images when you click on Home repeatedly. After testing latest windows nightly (clearing cache, restarting) I was unable to reproduce this behaviour after several attempts. I suppose some other change made in last couple of months fixed it. |