• wjmaclean's avatar
    Candidate fix for PointerEvent-OOPIF combination not working. · 8c15a423
    wjmaclean authored
    Prior to enabling PointerEvents, OOPIFs with TouchEvent handlers worked.
    But with PointerEvents turned on, they fail. This happens because the
    InputRouterImpl sending the touch events to the OOPIF never gets
    notified of the current TouchAction, in turn because ChromeClientImpl
    sends the TouchAction notification via RenderView and not the
    RenderWidget serving the OOPIF.
    
    Prior to PointerEvents this was not an issue, as the touch events
    would continue to flow regardlesss. But with PointerEvents, touch
    events are blocked after a TouchScrollStart is issued.
    
    This CL plumbs a LocalFrame* parameter into ChromeClient::setTouchAction
    so the notification can be sent via the correct channel.
    
    BUG=680158
    
    Review-Url: https://codereview.chromium.org/2626133002
    Cr-Commit-Position: refs/heads/master@{#443302}
    8c15a423
WebPagePopupImpl.cpp 21 KB