http://www.markledford.com/blog/2010/05/18/hash-anchors-using-in-a-swf-url-will-break-preloaders-due-to-a-player-bug/ Documenting the trials and triumphs of a mobile / front end web developer Thu, 02 Feb 2012 09:48:56 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://www.markledford.com/blog/2010/05/18/hash-anchors-using-in-a-swf-url-will-break-preloaders-due-to-a-player-bug/comment-page-1/#comment-18184 Ben Wed, 19 May 2010 08:50:50 +0000 http://www.markledford.com/blog/?p=122#comment-18184 Don't know if it applies to your situation but whenever I implement SWFAddress in my projects I always allow for alternate deeplinking via URL with params. When the app/site first loads I check for valid params and convert them to a swfaddress. Eg. you could load with "?page=pagename" added to the page or swf url, then check for 'page' and change the url with swfaddress to "#/pagename" This also helped with some bookmarking/sharing services that stripped out the anchor from any submitted urls. If I have bookmarking/sharing scripts in the app I use the URL with params rather than the swfaddress. Don’t know if it applies to your situation but whenever I implement SWFAddress in my projects I always allow for alternate deeplinking via URL with params. When the app/site first loads I check for valid params and convert them to a swfaddress.
Eg. you could load with “?page=pagename” added to the page or swf url, then check for ‘page’ and change the url with swfaddress to “#/pagename”
This also helped with some bookmarking/sharing services that stripped out the anchor from any submitted urls. If I have bookmarking/sharing scripts in the app I use the URL with params rather than the swfaddress.

]]>