Updates:
Status: Started
Comment #4 on issue 4684 by [EMAIL PROTECTED]: Back button loses
functionality after refresh with hash links.
http://code.google.com/p/chromium/issues/detail?id=4684
This problem is because RenderView::UpdateSessionHistory gets the previous
state of
the URL and then sends it upstream to the browser. This includes the
previous
reference fragment. When you press reload, the previous state is ...#b and
this is
sent up. However, it uses the current page ID.
WebContents::UpdateState sees the page ID as being the current one, but the
URL being
the old one. Then it updates the URL with the the "old" one (...#b) when
you're
reloading ...#c.
This seems pretty messed up. If my r2201 regressed this, it's only because
the old
code was somehow covering this problem up. I think it's a longstanding
problem. It's
definitely invalid to update the state using the previous URL and the
current page
ID.
It may be good enough for the branch to just not update the URL in
WebContents. There
will be some brokenness as a result of this weird behavior (not exactly
sure what,
specifically, it would be something like the form state gets lost), but
we've always
had this bug. I don't see why that code needs to update the URL (we should
already be
in sync due to the navigation messages).
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
