Bug 14261
| Summary: | Clicking back, forward, back changes forms and buttons on the page. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ben Spink <webkit> |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Major | CC: | ddkilzer, webkit |
| Priority: | P1 | Keywords: | InRadar |
| Version: | 523.x (Safari 3) | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | https://www.crushftp.com/demo/ | ||
Ben Spink
Going to the URL mentioned, and login as "demo" and "demo". Once logged in, click back, then forward, then back, then forward very quickly a few times. After a few iterations, the initial login page you had will suddenly change its button from "Login" to "Start Search". This "Start Search" string is not on the login.html page. Its on the authenticated page when you click the Search "button". However in the quick switching between pages, something gets crossed. I have placed a screenshot of what the bad page looks like once you login as "demo" and "demo". Its the file named "SafariRenderBug.png".
I have replicated this issue on XP with Safari 3.0.1, OS X 10.4.9 with latest Safari 3, and with the Nightly build 522.11. I have also replicated it on Safari 2.x on OS 10.3.9. So its an issue that has been around for a while and affects all versions I know of.
Once the button is messed up, other stuff in the form is apparently messed up to as using that form to authenticate produce other strange behavior as the correct data is not being sent.
Thanks,
Ben Spink
ben@crushftp.com
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
David Kilzer (:ddkilzer)
Confirmed with a local debug build of WebKit r23713 with Safari 3.0 (522.11) on Mac OS X 10.4.10 (8R218).
Marking as P1 for now since this is very strange behavior.
Note that when you're going back and forth between pages, don't give the browser time to reload each page.
David Kilzer (:ddkilzer)
<rdar://problem/5286440>
David Kilzer (:ddkilzer)
Can't reproduce the issue any longer. May be due to changes on the server side, or in Safari/WebKit.
Tested with Safari 3.2.1 on Mac OS X 10.4.11.