Closed tomwayson closed 8 years ago
@tomwayson It seems like the viewer is initialized without an options struct for the Simple
and Map (One Way)
examples which works fine. For the Map (Two Way)
example the viewer is initialized with and options struct that looks like this: { cover: false, detection: true }
. It is actually the Detection component
that is activated here that makes the call that causes the error. If you just initialize the viewer without the detection: true
setting I would expect it to work.
It is indeed a bug in MapillaryJS that the mixed content error occurs because of the Detection component
and I will create an issue for this. For your implementation I am suspecting that the Detection component
is not actually needed at this point (it is used to show rectangle overlays on top of the image)?
Thank you @oscarlorentzon.
Removing detection: true
worked!
https://tomwayson.github.io/ember-cli-mapillary/#/map-two-way
I did not have any particular reason to have included that other than the fact that I was copying code from the Web AppBuilder example. What's interesting is that that app works under HTTPS:
Glad it worked!
When testing the Web AppBuilder I'm actually receiving the same error message. I will forward the information. Thanks for pointing me in that direction.
When serving an app over HTTPS, and calling the viewer's
moveCloseTo()
method I see these errors in the console:Followed by this awesom rx.js
[object Object]
error:STR:
NOTE: those errors do happen when serving the app over HTTP.
Need to figure out a way to force viewer to make requests over same protocol used by the app.