Steps to reproduce:
1. Extract attached sample NotLoading project to a temporary folder.
2. Open NotLoading.html using any browser and make sure it loads and works (the counter should start from 0 and increment).
3. Close sample NotLoading.html browser window.
4. Open Windows Explorer window and maximize it.
5. Click Start and type in: "C:\Program Files\Internet Explorer\iexplore.exe" file://D:\WORK\Projects\ Flex4\NotLoading\bin-debug\NotLoading.html
(Make sure to use above the correct path to NotLoading.html)
6. Hit Enter and immediately click maximized Windows Explorer window to prevent Internet Explorer window from becoming foreground window and to force it behind Windows Explorer. Windows Explorer window must fully cover Internet Explorer window. Make sure Internet Explorer window opens but do not give it enough time to load our sample application. This step may require a few tries to get it right.
7. Wait for 30 seconds.
8. Switch to Internet Explorer and notice how the application just loads and the counter starts counting from 0. So waiting 30 seconds in step 7 did not make any difference. The application was not loading during that time.
The application does not load until Internet Explorer window becomes visible.
The application must load no matter if Internet Explorer is visible or no.
Workaround (if any):
Net result of this bug is that unattended functionality tests that are run using test automation tools (e.g. RIATest) are not working because Flex application never loads in the browser.