RESOLVED FIXED 233081
AX: _AXSCopyPathForAccessibilityBundle is going to be deprecated.
https://bugs.webkit.org/show_bug.cgi?id=233081
Summary AX: _AXSCopyPathForAccessibilityBundle is going to be deprecated.
Eric Liang
Reported 2021-11-12 17:09:49 PST
To support macOS Accessibility v2 runtime, on macOS there are two places where bundles can live. By doing so, `_AXSCopyPathForAccessibilityBundle` will going to be deprecated because it won’t always return the correct path you would expect .
Attachments
Patch (4.28 KB, patch)
2021-11-12 17:16 PST, Eric Liang
no flags
Patch (4.27 KB, patch)
2021-11-15 13:42 PST, Eric Liang
no flags
Eric Liang
Comment 1 2021-11-12 17:10:04 PST
rdar://85362881 (_AXSCopyPathForAccessibilityBundle is going to be deprecated.)
Radar WebKit Bug Importer
Comment 2 2021-11-12 17:10:05 PST
Eric Liang
Comment 3 2021-11-12 17:16:35 PST
Andres Gonzalez
Comment 4 2021-11-15 11:33:09 PST
(In reply to Eric Liang from comment #3) > Created attachment 444127 [details] > Patch --- a/Source/WTF/ChangeLog +++ a/Source/WTF/ChangeLog + _AXSCopyPathForAccessibilityBundle is going to be deprecated. Extra space at the beginning of the line. + To support macOS Accessibility v2 runtime, on macOS there are two places where bundles can live. By doing so, `_AXSCopyPathForAccessibilityBundle` will going to be deprecated because it won’t always return the correct path you would expect . Extra space before the period. --- a/Source/WebKit/ChangeLog +++ a/Source/WebKit/ChangeLog + To support macOS Accessibility v2 runtime, on macOS there are two places where bundles can live. By doing so, `_AXSCopyPathForAccessibilityBundle` will going to be deprecated because it won’t always return the correct path you would expect . Extra space before the period.
Eric Liang
Comment 5 2021-11-15 13:42:24 PST
EWS
Comment 6 2021-11-15 17:03:07 PST
Committed r285841 (244272@main): <https://commits.webkit.org/244272@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 444301 [details].
Note You need to log in before you can comment on or make changes to this bug.