-
Notifications
You must be signed in to change notification settings - Fork 1
Fix iframe #3
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
base: master
Are you sure you want to change the base?
Fix iframe #3
Conversation
tibetsprague
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm, id like to understand why this works before agreeing that this is the best solution. because this seems like it could break the iframe map
Inserted geojsonEvents function as needed for vue instance of iframe.
|
I looked into it further and iframe does need the geojsonevents function but the order they are initialized in vue affect the view of event map. I'm still investigating why the vue order matters, i'm assuming it has something to do with them sharing the same map id. |
|
That sounds very likely
… On Nov 22, 2017, at 2:44 PM, Mateo Balcorta ***@***.***> wrote:
I looked into it further and iframe does need the geojsonevents function but the order they are initialized in vue affect the view of event map. I'm still investigating why the vue order matters, i'm assuming it has something to do with them sharing the same map id.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAOnVY4LVktIRSbOhMVchR0K25zdJXpks5s5KO5gaJpZM4QoBRe>.
|
|
Change vue template based on href location. |
Change order of iframe initialization and removed duplicate function from iframe.js