-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application does not work in IE7 #18
Comments
Thanks for the bug report, Alan. I don't have access to Windows VM at the moment (which explains why it's not working in the first place) but I'd love a detailed bug report or even a patch if you think you know how to fix it. I'll be at my folks place over Thanksgiving, which is a good time for me to debug Windows issues. I'll make sure to take a look when I'm home. 😉 |
I was able to confirm this bug exists. I tried to see if I could find a relevant stack trace but there were no errors in the console. I was able to replicate it by opening IE 10 in IE 7 quirks mode. Is there anything else I can do? |
Is there an online version of the site with this problem? Testing on browserstack.com, I was able to open adopt-a-hydrant.herokuapp.com but the map was too wide for the page (it appears further down on the page, below the left sidebar). If this is an older version of the code, the two main IE JS bugs that I look for are: console.log (which isn't supported unless you're debugging, so anyone debugging the site will see no problems) and a comma at the end of JSON or JS objects (syntax error in IE) |
Actually, mapmeld, it looks like browser stack is replicating the problem exactly. I think zzolo and I were both experiencing the same issue you described. I did not realize if you scrolled down the map was there. It looks like this is a layout issue in IE7. |
Specifically the map does not work. I was not able to debug fully yet, but wanted to get this issue in. There were a number of errors that popped up.
I don't think it is an issue with Google Maps as it should support IE7 still.
More, real information coming soon.
The text was updated successfully, but these errors were encountered: