User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:22.214.171.124) Gecko/2008070208 Firefox/3.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:126.96.36.199) Gecko/2008070208 Firefox/3.0.1 Often times flash applications use the anchor section of the URL to store the state of the application (deeplinking). If an anchor (aka. hash string, deeplink) is included in the URL when loading the page, the flash player seems to wait till the entire SWF is loaded before displaying the first frame. The normal flash player behaviour is (and has always been) that when a frame on the root timeline gets loaded (and all of it's dependancies) the playhead moves forward into this frame. This is the mechanism used to display the vast majority of modern flash preloaders (it is used in all flex apps), meaning that these apps will never display a preloader when there is an anchor in the URL. Reproducible: Always Steps to Reproduce: 1. If you connection is to fast to see the issue, throttle your connection with a debugging tool (Charles is the best, http://www.charlesproxy.com/). 2. Load the aforementioned website (http://www.openuptomail.com.au) without an anchor (to witness the correct performance). 3. Clear your cache (again Charles can help with toggling caching). 4. Load the website with an anchor (http://www.openuptomail.com.au#tangibility). Actual Results: The page will remain white until the entire app has loaded. Expected Results: The page should display the preloader even when an anchor is in the URL.
This is a mass search for bugs that are in the Firefox General component, are UNCO, and have not been changed for 800 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the bug, please update this bug. If the issue is gone, please set the resolution to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.