Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
There seem to be a know issue with IE which doesn’t respond to URLs that have # sign in them.
See for example: https://mootools.lighthouseapp.com/projects/2706/tickets/638-request-fails-when-url-has-hash-in-ie7
As we use # quite frequently in out GWT based application we are lacking support for IE7 users who want to browse the site.
Is there any known workaround for GWT other than modifying the URL?
I think I finally figured out what the problem is.
Our gwt application is sitting as an iframe inside another HTML file so setting the gwt history support
has to be done in the outer HTML rather than the gwt one.
This gwt script was meant to support browsers such as IE6 and IE7 which don’t have the onhashchange event implemented.