RESOLVED DUPLICATE of bug 3580 15486
REGRESSION: Reload causes WebKit to *forget* fragment URLs 
https://bugs.webkit.org/show_bug.cgi?id=15486
Summary REGRESSION: Reload causes WebKit to *forget* fragment URLs
Eric Seidel (no email)
Reported 2007-10-12 23:16:32 PDT
Reload causes WebKit to *forget* fragment URLs See attached test case. Notice how the behavior is different when the page is first loaded (or loaded by hitting enter in the url bar, or dropping the file onto Safari) than when you hit "reload". Specifically the urls lose all of their fragments on reload!
Attachments
test case (1.91 KB, text/html)
2007-10-12 23:27 PDT, Eric Seidel (no email) 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Eric Seidel (no email)
Comment 1 2007-10-12 23:27:52 PDT
Created attachment 16651 [details] test case This actually behaves differently than my non-reduced (multi-file) test case. I may have to re-reduce that one to something that forgets the fragments all together. This one seems to remember them (but incorrectly!?)
Eric Seidel (no email)
Comment 2 2007-10-13 00:35:24 PDT
After further testing, this is a regression (albeit a strange one) from Safari 2.
Alexey Proskuryakov
Comment 3 2007-10-13 00:36:23 PDT
I'm surprised that pressing Enter in address bar and actually pressing Cmd+R produces different results - I thought both were supposed to perform the same action.
David Kilzer (:ddkilzer)
Comment 4 2007-11-28 23:00:02 PST
<rdar://problem/5619358>
Cameron Zwarich (cpst)
Comment 5 2008-03-21 18:43:49 PDT
(In reply to comment #3) > I'm surprised that pressing Enter in address bar and actually pressing Cmd+R > produces different results - I thought both were supposed to perform the same > action. I don't know whether they are supposed to do the same thing, but they don't. Hitting enter in the address bar will call FrameLoader::createHistoryItem(), but reloading doesn't do the same thing.
Cameron Zwarich (cpst)
Comment 6 2008-03-22 02:34:41 PDT
*** This bug has been marked as a duplicate of 3580 ***
Note You need to log in before you can comment on or make changes to this bug.