Working on a page that redirects users to an installed application or a webpage as a fallback. This is implemented using ClientScript.RegisterStartupScript when the page loads, with a Javascript snippet like this:
<script type='text/javascript'>var a = window.location.search; setTimeout(function(){ window.location.pathname = '/Fallback.aspx'}, 500); window.location='myapp://open' + a;</script>
In Google Chrome, the redirection to the Fallback page works perfectly if 'myapp://open' fails. But in Internet Explorer, it only works with a timeout value of 100 or lower. The issue arises in Firefox, where the redirect never seems to work despite trying different timeout values. Any ideas why and how to resolve this specifically for Firefox?
Appreciate any insights you can offer.
UPDATE: Firefox displays an error page titled "The address wasn't understood" stating that the protocol (myapp) is not associated with any program.
UPDATE: To test this, replace '/Fallback.aspx' with 'www.google.com' in the code. In IE or Chrome, it will fail to open myapp://open and redirect to Google as intended. However, in Firefox, you may encounter the protocol unrecognized error and the fallback redirection won't happen. I hope this clarifies the situation and apologies for any confusion in my original question.