[Webkit-unassigned] [Bug 135689] New: AX: event.target should sometimes be a descendant element on AXPress-triggered mouse clicks

[bugzilla-daemon at webkit.org]

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

           Summary: AX: event.target should sometimes be a descendant
                    element on AXPress-triggered mouse clicks
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Accessibility
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jcraig at apple.com
                CC: webkit-bug-importer at group.apple.com


AXPress sometimes triggers the click event (and other mouse events) on a different element than a real mouse click would use. We should try using hit-testing at the center of the clickable (link, button, etc.) to determine the element on which to initiate the mouse events. In some cases, it may be better to a descendant node as the event.target. If the center point hit-test results in a node that is not a descendant, we should ignore it and fire the event on the original element.

To be clear, I don’t think WebKit is doing anything wrong, but there are times when web authors do silly things. VO+Space doesn’t work, but routing the mouse to an element and triggering a simulated mouse click does. This idea is mainly to work around those web authoring problems, and make it so that AXPress works in more scenarios.

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