Bug 233791 – AX: Attempting to play local media files as part of a speech study causes Safari to hang.

• Component: Accessibility
• Status: RESOLVED WONTFIX

[chris fleizach]

1. Enable VoiceOver.
2. Navigate using VoiceOver to the first audio file and press space bar when focused on the play button.

Actual Results: Safari does not play the audio and instead becomes unresponsive.

Expected Results: Playing the files should work as expected, even if they are local.

<rdar://problem/85990360>

[Radar WebKit Bug Importer]

<rdar://problem/85994691>

[chris fleizach]

Created attachment 445790 [details]
patch

[Tyler Wilcock]

Comment on attachment 445790 [details]
patch

View in context: https://bugs.webkit.org/attachment.cgi?id=445790&action=review

> Source/WebKit/ChangeLog:9
> +        If we send a sync message after user interaction, we need to inform that the process will susped so that VoiceOver doesn't get stuck.

Typo. susped --> suspend

[Eric Carlson]

Comment on attachment 445790 [details]
patch

View in context: https://bugs.webkit.org/attachment.cgi?id=445790&action=review

> Source/WebKit/ChangeLog:9
> +        If we send a sync message after user interaction, we need to inform that the process will susped so that VoiceOver doesn't get stuck.

s/susped/suspend/

[chris fleizach]

Created attachment 445806 [details]
patch

[Andres Gonzalez]

(In reply to chris fleizach from comment #5)
> Created attachment 445806 [details]
> patch

Couldn't we change sendSync(...) to SendSyncOption::InformPlatformProcessWillSuspend by default? So that it doesn't break again next time somebody adds another call.

[chris fleizach]

(In reply to Andres Gonzalez from comment #6)
> (In reply to chris fleizach from comment #5)
> > Created attachment 445806 [details]
> > patch
> 
> Couldn't we change sendSync(...) to
> SendSyncOption::InformPlatformProcessWillSuspend by default? So that it
> doesn't break again next time somebody adds another call.

I gather there are a lot of sync calls. When we inform it will suspend it causes VO to not be able to interact with the app until it’s done. Given the lag in posting and processing these changes I think it would break normal navigation. Our problem is with synchronous calls that wait on safari to do expensive work. Most of the send sync calls are fairly straightforward. This is my impression on why we can’t just do this always

[chris fleizach]

Looked into this more and something is not lining up. this patch would allow VO to navigate Safari again, but that won't help the WebContnt process being blocked.