Copy link to clipboard
Copied
Good Afternoon,
We are experiencing the following issue while trying to test a Flash application on Windows 10 while using JAWS:
A Flash application uses “ExternalInterface.call” to call a JavaScript function and passes an argument of a URL string. The JavaScript function uses “window.open” to open a new browser window with the URL. This causes Internet Explorer 11 to freeze and display the following message “A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.” Both the base screen that has the Flash file and the popup refresh.
This issue only occurs while using JAWS, Windows 10, Flash, and IE11. This does not happen on Windows 7.
Specs of Computer with issue:
This is a complete shot in the dark, but what happens if instead of the called function directly executing window.open, it instead uses setTimeout to schedule another function to do it a fraction of a second later?
Note that IE9 and below don't support passing parameters via setTimeout.
At the very least it might help you isolate exactly which stage of the operation is causing the crash.
Copy link to clipboard
Copied
This is a complete shot in the dark, but what happens if instead of the called function directly executing window.open, it instead uses setTimeout to schedule another function to do it a fraction of a second later?
Note that IE9 and below don't support passing parameters via setTimeout.
At the very least it might help you isolate exactly which stage of the operation is causing the crash.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now