You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclustererp
lus/src/markerclusterer.js
/**
* The default root name for the marker cluster images.
*
* @type {string}
* @constant
*/
MarkerClusterer.IMAGE_PATH =
"http://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclustererp
lus/images/m";
What steps will reproduce the problem?
1. load
https://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclusterer/
examples/simple_example.html
2. The page at
'https://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclusterer
/examples/simple_example.html' was loaded over HTTPS, but displayed insecure
content from
'http://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclusterer/
images/m1.png': this content should also be loaded over HTTPS.
3.
Expected result:
Actual result:
Version: ###
Browser / Operating System:
[Chrome / Win7]
Additional comments:
[Enter any additional comments about the bug here.]
*********************************************************
Tip: Star this issue (next to title) to receive notifications of status
changes against this issue, also used as a gauge for how many people are
interested in seeing it resolved.
*********************************************************
Original issue reported on code.google.com by [email protected] on 23 Oct 2014 at 11:28
The text was updated successfully, but these errors were encountered:
The problem can be solved by overriding the imagePath option using it's httpS
version like :
mcOptions = {
imagePath:
"https://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclusterer
plus/images/m"
};
markerCluster = new MarkerClusterer(map, MarksToDisplay, mcOptions);
Cdlt,
Bertrand.
Original issue reported on code.google.com by
[email protected]
on 23 Oct 2014 at 11:28The text was updated successfully, but these errors were encountered: