1 person found this helpful
I have also sometimes this kind of unusual behaviour...Try to do the following and just check whether its working for you..
Say if your domain is http://www.yourdomain.com/ and you are currently in YourPage.html and you want to navigate to yourotherpage.html then you simply try to use the relative path instead of absloute path..
navigateToURL(new URLRequest("http://www.yourdomain.com/pages/yourpage.html"), '_parent'); ------ absolute path
navigateToURL(new URLRequest("yourotherpage.html"), '_parent'); --- relative path
Hope this may work for you...Off the top of my head I think I used the same solution once long back and it worked for you.
If this post answers your question or helps, please kindly mark it as such.
If you delayed calling navigateToURL, popup blockers might block it.
Bhaskar: Thanks, that did clear up the issue with some people. There are still users having the problem, though.
harUI: What do you mean by "delayed?" Currently, it is set up so that after they click the Finish button, the URL is generated based on their answers to the questions and stored in whereTo. Then I call navigatetoURL as I said before.
Are you saying that I should set it up so that the URL generates BEFORE they click the finish button and then have calling navigateToURL be the ONLY thing that happens after they click the button? I shall try that, but if you mean something different, please let me know. I don't BELIEVE the users with the issue are having a popup blocker issue, but I can't get to the computers and just have to trust the users at this point (which is frustrating).
Some configurations only allow navigateToURL to work in response to a mouse
click. Any delay from asking a server for a response or even using
callLater will allow the handling of the mouse gesture to finish before
navigateToURL is called and not allow the popup.
I tried making it so that the only command the finish button executed was navigatetoURL. I thought it had worked, but I just got a phone call. Same issue. Any other ideas? Anyone?
If your users have the time to try a test app, deploy a real simple app and
see if the users can make it fail.
I've got a test app for the next time I have a user willing to cooperate (the nature of this app is that a user only has to run it once, ever, so they aren't as cooperative as they could be).
In the mean while, I changed it to launch the URL using ExternalInterface and it STILL is not working for some users.
Any other ideas?