Nothing uses AXAriaAttributeChanged, but we still spend time processing it through the notification pipeline (postNotification -> m_notificationsToPost -> updateIsolatedTree(notifications) + postPlatformNotification(notifications)).
<rdar://problem/87619004>
Created attachment 449227 [details] Patch
Comment on attachment 449227 [details] Patch we're sure GTK/Win don't use this?
Yeah, quite sure. Windows doesn't handle it, and doesn't have a fallthrough in postPlatformNotification for notifications that aren't explicitly handled by name (it returns early if given an unexpected notification). ATK / ATSPI seems to be the same, but CC'd Carlos to confirm. Carlos, can you confirm that the ATK / ATSPI ports don't and won't use this?
(In reply to Tyler Wilcock from comment #4) > Yeah, quite sure. Windows doesn't handle it, and doesn't have a fallthrough > in postPlatformNotification for notifications that aren't explicitly handled > by name (it returns early if given an unexpected notification). ATK / ATSPI > seems to be the same, but CC'd Carlos to confirm. > > Carlos, can you confirm that the ATK / ATSPI ports don't and won't use this? Ok if we pass all the builds probably ok. It can always be added back if we need it
Committed r288056 (246076@main): <https://commits.webkit.org/246076@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 449227 [details].