[Webkit-unassigned] [Bug 98139] New: Disambiguate resultFramePoint and original hit-test point

[bugzilla-daemon at webkit.org]

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

           Summary: Disambiguate resultFramePoint and original hit-test
                    point
           Product: WebKit
           Version: 420+
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: allan.jensen at digia.com


HitTestResult derives from HitTestLocation and thereby doubles as a point. In the current algorithm on render-tree level, this point is always both the original hit point, and the point in the result frame, because it stays within the same frame. The HitTestResult returned by EventHandler::hitTestResultAtPoint however descends into sub-frames, and currently returns a HitTestResult which contains a point transformed into result-frame coordinates.

The problem with this semantics is that descending into sub-frames is also necessary for area-based hit-testing, and the concept of the frame of the result become meaningless when the results can be from multiple frames.

The issue was seen with patch landed and reverted in bug #95204. As a stepping stone before relanding a solution there, we need to make the users of HitTestResult explicitly use either the result-frame point or original hit-test point. This is likely to solve a some corner-case bugs as well.

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