Open hardnett opened 7 years ago
I am guessing that this has to do with how the browser gets the current location, maybe firefox does something differently, because I know I wrote this and tested it in chrome.
With the changes made to fix a bug with initial load place (issue #56), this issue should not occur anymore, safari and firefox were loading correct before, and chrome was wrong, now all 3 should be working correctly)
I missed an error with firefox, reopened issue and am with firefox to close the issue
Moved this out of current sprint, I am currently working with the sidebar issue #16 and the null response error #53 and #61, I want to push this back until after these are all finished (I can't work on 3 sprints at once)
When loading the initial location, the results are different on these 3 browsers:
Safari:
FireFox:
Chrome:
Safari and Chrome are handling it in the same way, Firebox is completely different.