Bug 125608

Summary: AX: WebKit sends wrong screenY value for AXPress-triggered events
Product: WebKit Reporter: James Craig <jcraig>
Component: AccessibilityAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
test case none

James Craig
Reported 2013-12-11 18:07:32 PST
AX: WebKit sends wrong screenY value for AXPress-triggered events
Attachments
test case (1.30 KB, text/html)
2013-12-11 18:09 PST, James Craig 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
James Craig
Comment 1 2013-12-11 18:09:59 PST
Created attachment 219024 [details] test case
James Craig
Comment 2 2013-12-11 18:11:39 PST
Load the test case, and perform a mouse click in the dead center of the buttons. Then perform a VoiceOver-triggered AXPress. They event objects match up within a pixel or two except for screenY, which is way off.
James Craig
Comment 3 2013-12-11 18:17:01 PST
<rdar://problem/15643218>
James Craig
Comment 4 2015-01-15 00:25:30 PST
Looks like several others are way off now, too: y, clientY, layerY, pageY, and screenY are all wrong. Both offsetX and offsetY values are missing, too. Mouse [x: 183, y: 18, clientX: 183, clientY: 18, layerX: 183, layerY: 18, offsetX: 20, offsetY: 8, pageX: 183, pageY: 18, screenX: 183, screenY: 126] VoiceOver [x: 183, y: 104, clientX: 183, clientY: 104, layerX: 183, layerY: 104, offsetX: 0, offsetY: 0, pageX: 183, pageY: 104, screenX: 183, screenY: 773]
Note You need to log in before you can comment on or make changes to this bug.