Bug 116756

Summary: AX: WKView is unable to set AXFocused to YES and does not handle keyboard events as expected
Product: WebKit Reporter: chris fleizach <cfleizach>
Component: AccessibilityAssignee: chris fleizach <cfleizach>
Status: RESOLVED FIXED    
Severity: Normal CC: aboxhall, apinheiro, commit-queue, dmazzoni, jdiggs, mario, thorton
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
patch thorton: review+

chris fleizach
Reported 2013-05-24 22:40:06 PDT
It appears that if AXFocused is set to YES on a web view that accepts text editing, the WebView does not become the first responder
Attachments
patch (2.62 KB, patch)
2013-05-24 22:45 PDT, chris fleizach 		thorton: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
chris fleizach
Comment 1 2013-05-24 22:45:37 PDT
Created attachment 202875 [details] patch
chris fleizach
Comment 2 2013-05-24 22:46:37 PDT
rdar://13925131
Tim Horton
Comment 3 2013-05-28 14:10:07 PDT
Comment on attachment 202875 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=202875&action=review > Source/WebCore/accessibility/mac/WebAccessibilityObjectWrapperMac.mm:3051 > + bool focus = [number intValue] != 0; NSNumber has boolValue... > Source/WebCore/accessibility/mac/WebAccessibilityObjectWrapperMac.mm:3058 > + page->chrome().client()->focus(); Could grab the chrome client in a local and reuse it on these three lines.
chris fleizach
Comment 4 2013-05-28 14:47:57 PDT
http://trac.webkit.org/changeset/150836
Note You need to log in before you can comment on or make changes to this bug.