[Webkit-unassigned] [Bug 61543] New: Inform ChromeClient touch events are not needed by the webpage when navigating away from the page instead of in both Document:detach/CachedFrame

[bugzilla-daemon at webkit.org]

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

           Summary: Inform ChromeClient touch events are not needed by the
                    webpage when navigating away from the page instead of
                    in both Document:detach/CachedFrame
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: dinu.jacob at Nokia.com


Currently, the chrome client is informed that the touch events are not needed in Document::detach / CachedFramed constructor. 

When loading a new page, the old page is added to page cache and the chrome client is informed that touch events are not needed anymore in the CachedFrame constructor. However, if the page cache capacity has been reached, the oldest item is marked to be removed from the cache and a timer is started. The item is removed from cache when the timer expires. When the item is removed, Document:detach is called which informs (incorrectly) chrome client that touch events are not needed. If the current page loaded has touch event listeners, it will not get touch events anymore.

As needTouchEvents method takes only a boolean, there is no indication that the flag was reset for the older document being detached. It might be better to reset the flag at the time we navigate away from the current page.

Patch to follow shortly.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.