[Webkit-unassigned] [Bug 48385] Add WebKit SPI to scale a WebView

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Oct 27 11:44:15 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=48385


Darin Adler <darin at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #72044|review?                     |review+
               Flag|                            |




--- Comment #6 from Darin Adler <darin at apple.com>  2010-10-27 11:44:15 PST ---
(From update of attachment 72044)
View in context: https://bugs.webkit.org/attachment.cgi?id=72044&action=review

> WebCore/page/Frame.cpp:163
> +    , m_pageScaleFactor(1)

I’m disappointed to see more being added to Frame. I’ve been trying to cut down on operations in Frame, and would normally look for a different home for such a thing. On the other hand, I was unsuccessful at moving the page and text zoom factor out.

If this does have to be on the central “god object” maybe it makes more sense to put it on Page than on Frame.

> WebCore/page/Frame.cpp:967
> +    if (m_pageScaleFactor == scale)
> +        return;

Will this do the right thing in the case where the scale factor is the same, but the origin is different?

> WebCore/page/Frame.cpp:979
> +    // Update the scroll position to the origin of the scale.
> +    if (FrameView* view = this->view())
> +        view->setScrollPosition(IntPoint(origin.x(), origin.y()));

I really don’t understand why this is the right thing to do and why we need a single function call that does both of these things? Can’t we set the scroll position another way.

-- 
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