Issue 3912: Unfork FrameLoader.cpp changes made to support the
window.history object
http://code.google.com/p/chromium/issues/detail?id=3912
New issue report by [EMAIL PROTECTED]:
Our changes to FrameLoader.cpp make the query of the BackForwardList
asynchronous. This is unnecessary for ports other than Chromium, so the
WebKit folks are (understandably) reluctant to take such a patch upstream.
It's best if we fix this on our side.
jabdelmalek came up with a clever idea, which I'm going to implement:
"fake" a HistoryItem with an URL like "history://go/offset" to indicate a
back/forward navigation to the given offset. We can return the HistoryItem
synchronously, but handle the navigation ourselves asynchronously.
Issue attributes:
Status: Started
Owner: [EMAIL PROTECTED]
Labels: Type-Bug Pri-1 OS-All Area-Misc
--
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
-~----------~----~----~----~------~----~------~--~---
