Skip to content
  • tonikitoo@webkit.org's avatar
    Be more restrictive when adding ScrollableArea's to FrameView's ScrollableArea's map · d911ca3f
    tonikitoo@webkit.org authored
    https://bugs.webkit.org/show_bug.cgi?id=79611
    
    Reviewed by James Robinson.
    Patch by Antonio Gomes <agomes@rim.com>
    
    Source/WebCore:
    
    As of today, any FrameView attached to the Widget-tree or any
    RenderLayer whose corresponding RenderBox's style has a 'overflow'
    property set to 'auto' is cached in its containing scrollable areas set.
    We could be more restrictive about what we in fact want to
    cache as scrollable areas, by checking if the element as an overflow
    (i.e. more content than its viewport).
    
    * page/FrameView.cpp:
    (WebCore::FrameView::setFrameRect):
    
    Whenever the viewport changes, check if we have an scrollable/overflowed
    content, and update the cache accordingly.
    
    (WebCore::FrameView::setContentsSize):
    
    Whenever the contents size changes, check if we have a scrollable/overflowed
    content, and update the cache accordingly.
    
    (WebCore::FrameView::calculateScrollbarModesForLayout):
    
    Introduces a way to query for the scrol...
    d911ca3f