Summary: | The currentItem fixup done by BackForwardList::pushStateItem should be moved into HistoryController::pushState | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Darin Fisher (:fishd, Google) <fishd> | ||||
Component: | Page Loading | Assignee: | Darin Fisher (:fishd, Google) <fishd> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | abarth, beidson, eric, mihaip, webkit.review.bot | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Description
Darin Fisher (:fishd, Google)
2010-07-30 16:14:32 PDT
Created attachment 63124 [details]
v1 patch
Note: the dereference of m_previousItem in HistoryController::pushState is protected by the null check of m_currentItem at the top of the function. This is because createItemTree has the side-effect of assigning m_previousItem. Comment on attachment 63124 [details] v1 patch > - HistoryItem* targetItem = m_frame->loader()->history()->currentItem(); LOL, m_frame->loader()->history() is a roundabout way of writing "this"! (In reply to comment #3) > (From update of attachment 63124 [details]) > > - HistoryItem* targetItem = m_frame->loader()->history()->currentItem(); > > LOL, m_frame->loader()->history() is a roundabout way of writing "this"! Yup, and I was so proud of myself for avoiding HistoryItem::targetItem() too ;-) http://trac.webkit.org/changeset/64402 might have broken SnowLeopard Intel Release (Tests) (In reply to comment #5) > http://trac.webkit.org/changeset/64402 might have broken SnowLeopard Intel Release (Tests) ^^^ fixed This patch appears to have been landed. |