Skip to content
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

Fix issue with maps where it doesn't show pins when switching between facility list and facility #84

Open
jonminter opened this issue Dec 23, 2015 · 5 comments · Fixed by #89
Labels

Comments

@jonminter
Copy link
Contributor

No description provided.

@jonminter
Copy link
Contributor Author

Was working locally but when deployed still see the issue

@patricknowlan
Copy link
Contributor

I think i fixed this issue by adding an ng-if to the map that checks that the data has been loaded before rendering the map. In pull request #114. This might also be a duplicate of #108 which I closed. I noticed a new issue where the map does not show pins when the state changes based off of navigating screens using the browsers back button.

@patricknowlan
Copy link
Contributor

Should we create a new issue or track it here?

@patricknowlan
Copy link
Contributor

I think this is an issue with the state.

jonminter pushed a commit that referenced this issue Dec 29, 2015
…isplay map like in FacilityController, hopefully this will fix the browser back button map issues #84
jonminter added a commit that referenced this issue Dec 29, 2015
Added resize event trigger to facility page #84
@patricknowlan
Copy link
Contributor

Looks like this is partially fixed. It works for navigating back and forth between the facility list and facility page but the map will not work if you press back until you hit the dashboard page and select a new state. It will require the user to refresh their page once they land on the facility list view in order to view the map

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants