Summary: | AX: WK2: Safari extension installation hangs Safari and VoiceOver | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | chris fleizach <cfleizach> | ||||
Component: | Accessibility | Assignee: | chris fleizach <cfleizach> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | andersca, ap, beidson, commit-queue, jberlin, webkit-bug-importer | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Description
chris fleizach
2013-12-05 10:42:02 PST
Created attachment 218524 [details]
patch
This is super scary. With this patch, dispatchDecidePolicyForResponse will have entirely different behavior when accessibility is enabled. If you can prove that it is safe to spin run loop here, I suggest making it unconditionally. Otherwise, we might need a deeper change to ho extensions are installed. (In reply to comment #4) > If you can prove that it is safe to spin run loop here, I suggest making it unconditionally. > > Otherwise, we might need a deeper change to ho extensions are installed. This seems not that much different from javascript alerts where we do unsigned syncSendFlags = (WebCore::AXObjectCache::accessibilityEnabled()) ? CoreIPC::SpinRunLoopWhileWaitingForReply : 0; WebProcess::shared().parentProcessConnection()->sendSync(Messages::WebPageProxy::RunJavaScriptAlert(webFrame->frameID(), alertText), Messages::WebPageProxy::RunJavaScriptAlert::Reply(), m_page->pageID(), CoreIPC::Connection::NoTimeout, syncSendFlags); That code has been in for 2 years, and we do have one case where it has proven to be unsafe (https://bugs.webkit.org/show_bug.cgi?id=123828) which I am very close to having a fix for. Should we make it unconditional in that case? Anders and Brady are really the ones who should make the call on whether it's acceptable design to spin the run loop here. (In reply to comment #6) > Should we make it unconditional in that case? > Not sure. I think Anders and Darin helped me resolve the javascript case in the past, so (echoing you) they'll probably be able to speak to that more. Thanks > Anders and Brady are really the ones who should make the call on whether it's acceptable design to spin the run loop here. Comment on attachment 218524 [details]
patch
I think this looks good.
Comment on attachment 218524 [details] patch Clearing flags on attachment: 218524 Committed r160197: <http://trac.webkit.org/changeset/160197> All reviewed patches have been landed. Closing bug. |