17263 2008-02-09 14:33:27 -0800 Acid3 test 80 (linktest onload didn't fire) fails on reload but passes on first run 2008-02-24 01:45:07 -0800 1 1 1 Unclassified WebKit WebCore JavaScript 528+ (Nightly build) Mac OS X 10.5 RESOLVED FIXED http://acid3.acidtests.org/ P2 Normal --- 17064 1 dev+webkit webkit-unassigned darin eric ian webkit oldest_to_newest 69949 0 dev+webkit 2008-02-09 14:33:27 -0800 If you run the Acid 3 test in ToT, you pass 79/100 tests, reloading it and running it again only passes 78/100 tests. Test 80 (linktest onload didn't fire) does not pass the second time. 69972 1 webkit 2008-02-09 15:52:37 -0800 Webkit r30109. Tens of Acid3 test runs and I haven't notice 79/100 score at all. 70112 2 darin 2008-02-10 12:39:33 -0800 I've seen this; we need to investigate. 70166 3 hyatt 2008-02-10 17:34:44 -0800 It never seems to pass for me. Maybe if I started with an empty cache. 70223 4 webkit 2008-02-11 03:13:23 -0800 Checked the Acid3 test again (it was changed a little - we pass only 79/100 now, red cat displays now). On the first run the test 80 failed (78/100). After reload the test passed (79/100). 70371 5 eric 2008-02-12 01:54:14 -0800 This and bug 16770 refer to the same Acid3 failure. Which is the real cause, I'm not sure. 70964 6 webkit 2008-02-17 12:19:15 -0800 The issue relies on onload so it turns my attention to behavior reported in bug 15137 or maybe in bug 14693. 71701 7 darin 2008-02-24 00:33:09 -0800 I believe the reason this test fails on reload may be that on reload the frame gets a new src attribute, but reload simply reloads the old URL. Firefox 2 fails the same way (I didn't try a Firefox 3 beta), and it's possible this is a feature, not a bug. When I wrote the regression test LayoutTests/fast/history/subframe-is-visited.html I worked around this by giving the frame a new name each time. It's possible Acid3 should be modified to do the same thing. Or maybe this truly is a bug. 71702 8 darin 2008-02-24 00:34:44 -0800 Hmm, after saying all that, I tested and with my latest fix, this seems to work even on reload. I'm going to say FIXED for this bug. 71706 9 ian 2008-02-24 01:19:08 -0800 The script manually changes the src="" during the test, so it shouldn't matter if reload reloads the old URI. 71709 10 darin 2008-02-24 01:45:07 -0800 (In reply to comment #9) > The script manually changes the src="" during the test, so it shouldn't matter > if reload reloads the old URI. Yes, I realize that. But when I tried a simple test case, the page that manually changed the src of the iframe element did not load that new src on either Safari or Firefox. I know that sounds crazy. Obviously I didn't understand the issue thoroughly since I can't explain it right now. But there's something unusual going on with frame reloading and dynamic changes to the iframe src attribute, in both browsers.