[Webkit-unassigned] [Bug 18992] Reset scroll position when loading new page
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sun May 11 00:30:05 PDT 2008
http://bugs.webkit.org/show_bug.cgi?id=18992
kevino at theolliviers.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Ever Confirmed|0 |1
------- Comment #3 from kevino at theolliviers.com 2008-05-11 00:30 PDT -------
(In reply to comment #2)
> (From update of attachment 21060 [edit])
> windowObjectCleared is definitely not the right place to be doing this. It's
> likely there is some underlying issue that is leading to the incorrect
> behaviour you're seeing -- none of the other ports call setContentsPos from
> within WebKit, which suggests to me that doing so for wx is papering over an
> issue elsewhere.
>
Yeah, poking around some more, I think the real issue is that we don't handle
FrameLoaderClientWx::transitionToCommittedForNewPage(), which deletes and
re-creates the FrameView, and that's probably how all the other ports end up
having their scroll positions reset.
--
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list