While revisiting issue 6018 [1], I accidentally stumbled across a potential issue while testing "links/001.xml". I've searched for object/iframe history issues but wasn't able to find anything related so here goes... Steps to reproduce: 1. Open any page to populate history (google [2], for example); 2. Open this issue's URL [3]; 3. Select "links/001.xml"; 4. Select any of the two blue shapes ("PASS" text is displayed, as result of navigating to "links/pass.txt"); 5. Press the back button; 6. (optional) Select any of the tests; Expected results: In step 4, the object should go back to "links/001.xml" or, in alternative, previous page (google, in the sample provided) would be displayed. In step 5, the object should be replaced with the selected link. Actual results: In step 5, the object disappears. This suggests that the back button didn't consider the object replacement steps, which may not be considered an issue. Step 6 seems to point towards incoherent behavior: the previously displayed document, "links/001.xml", is always shown independently of the document choice. It sounds like the object was cached and any document selection is assumed as the previous state. Additional information: I agree (marking as low priority and minor severity) that this is a somehow exotic navigation mechanism: by analyzing the document [3] source, an object is created on the fly, pointing out to the selected URL. Using direct URL navigation - first to any page [2], then to the specific test's URL [4] and pressing the blue shape - the back button behaves as expected. Version information: Browser - Webkit r39474 on Safari 3.2.1 Operating system - Windows XP SP3 Hope this helps, Helder Magalhães [1] https://bugs.webkit.org/show_bug.cgi?id=6018#c2 [2] http://www.google.com/ [3] http://hixie.ch/tests/adhoc/svg/svg-plugin-ua.html [4] http://hixie.ch/tests/adhoc/svg/links/001.xml