WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
120027
AXObjectCache's accessibilityEnhancedUserInterfaceEnabled should be initialized on process creation
https://bugs.webkit.org/show_bug.cgi?id=120027
Summary
AXObjectCache's accessibilityEnhancedUserInterfaceEnabled should be initializ...
Beth Dakin
Reported
2013-08-19 14:00:36 PDT
Right now we only call AXObjectCache::setEnhancedAccessibility() when AppKit sends us a notification indicating that the value has changed. We should not have to rely on that to properly initialize this value. <
rdar://problem/14736960
>
Attachments
Patch
(4.53 KB, patch)
2013-08-19 14:05 PDT
,
Beth Dakin
sam
: review+
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Beth Dakin
Comment 1
2013-08-19 14:05:48 PDT
Created
attachment 209120
[details]
Patch
chris fleizach
Comment 2
2013-08-19 14:16:06 PDT
Comment on
attachment 209120
[details]
Patch looks good to me
Sam Weinig
Comment 3
2013-08-19 14:43:47 PDT
Comment on
attachment 209120
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=209120&action=review
> Source/WebKit2/WebProcess/mac/WebProcessMac.mm:188 > + AXObjectCache::setEnhancedUserInterfaceAccessibility(parameters.accessibilityEnhancedUserInterfaceEnabled);
You can call setEnhancedAccessibility(parameters.accessibilityEnhancedUserInterfaceEnabled) here instead.
Beth Dakin
Comment 4
2013-08-19 14:53:57 PDT
Thanks, Sam!
http://trac.webkit.org/changeset/154302
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug