RESOLVED FIXED303936
[Accessibility] HAVE_ADDITIONAL_NS_ACCESSIBILITY_CONSTANTS's SDK check causes availability issues in back-deployment 
https://bugs.webkit.org/show_bug.cgi?id=303936
Summary [Accessibility] HAVE_ADDITIONAL_NS_ACCESSIBILITY_CONSTANTS's SDK check causes...
Elliott Williams
Reported 2025-12-10 12:04:53 PST
It changed from MIN_REQUIRED to MAX_ALLOWED in https://bugs.webkit.org/show_bug.cgi?id=303154, which is wrong -- these symbols need to be available at runtime, so we must check the deployment target. I'm not sure why this hasn't caused runtime failures, maybe it relates to how we redeclare NSAccessibility symbols?
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2025-12-10 12:04:59 PST
<rdar://problem/166243010>
Elliott Williams
Comment 2 2025-12-10 13:09:01 PST
Pull request: https://github.com/WebKit/WebKit/pull/55191
EWS
Comment 3 2025-12-16 14:46:59 PST
Committed 304546@main (08388a0dd480): <https://commits.webkit.org/304546@main> Reviewed commits have been landed. Closing PR #55191 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.