[Webkit-unassigned] [Bug 48809] Chromium WebKit API needs WebFrame::lastCommittedHistoryItem()
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Nov 4 14:03:17 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=48809
Darin Fisher (:fishd, Google) <fishd at chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #72605|review? |review-
Flag| |
--- Comment #2 from Darin Fisher (:fishd, Google) <fishd at chromium.org> 2010-11-04 14:03:17 PST ---
(From update of attachment 72605)
View in context: https://bugs.webkit.org/attachment.cgi?id=72605&action=review
> WebKit/chromium/src/WebFrameImpl.cpp:1006
> + return WebHistoryItem(viewImpl()->lastCommittedHistoryItem());
I think you can implement this using m_frame->loader()->history()->currentItem()
as that provides you with the last-committed history item for this frame.
This would allow you to eliminate a lot of code in this patch.
Come to think of it, I suspect that WebFrameImpl::currentHistoryItem is
incorrectly implemented. It is incorrectly accessing the currentItem of
the BackForwardList, which corresponds to the HistoryItem of the top-most
frame. If a user of the WebKit API wants the HistoryItem of the top-most
frame, then they should just use WebFrame::top()->currentHistoryItem().
In other words, currentHistoryItem is supposed to mean the same thing as
lastCommittedHistoryItem.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list