| Summary: | REGRESSION (r48687): Wachovia Online Billpay website broken | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Justin Hibbits <chmeeedalf> | ||||
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED DUPLICATE | ||||||
| Severity: | Normal | CC: | beidson, darin, dbates, mrowe, sam | ||||
| Priority: | P1 | Keywords: | InRadar, Regression | ||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Attachments: |
|
||||||
|
Description
Justin Hibbits
2009-10-24 11:54:17 PDT
Can you please provide a URL that can be used to reproduce this? https://www.wachovia.com is the top-level page. But an account is required in order to test the Bill Pay link. The actual bill pay link within the account realm is generated with javascript. I will note that this also occurs with Safari, using the OS X Webkit nightly svn revision 50006. Created attachment 41827 [details] Reduction Here is a reduction. When you click on Pay Bills the browser is taken to the page: https://onlineservices.wachovia.com/NASApp/NavApp/Titanium (i.e. the link actually submits a form with some parameters). The issue seems to be caused by the script that appears in the <head> of the HTTP response: <script>history.go(1)</script>. This script causes the browser to redirect to the next page in the history (i.e. equivalent to clicking the Forward button in the browser). But, no such history entry exists yet! (it would only exist if, say, we clicked on a link on this page then pressed the Back button in the browser). Confirmed this is a regression that affects Macintosh PowerPC, Macintosh Intel, and Windows XP using r50039 for Mac, r49956 for Windows. Works in Safari Version 4.0.3 (5531.9). This regression first appeared in nightly build r48730. If I have some time, I'll try to bisect from r48680 (works) to r48730 (does not work) and find the culprit revision. Confirmed r48687 is the cause, <http://trac.webkit.org/changeset/48687>. CC'ing Darin and Sam. Brady fixed two issues that were fallout from r48687 today. Does this still occur with ToT? This is almost certainly a dupe of http://webkit.org/b/30424 and was almost certainly fixed by http://trac.webkit.org/changeset/50111 but I can't verify right now. *** This bug has been marked as a duplicate of bug 30424 *** |