Open GoogleCodeExporter opened 8 years ago
This is right answer! The protocol of the including page should be respected.
So no warnings about unsecure content are displayed when used over https.
Original comment by adityava...@gmail.com
on 24 Jan 2013 at 10:14
[deleted comment]
This makes the infobubble unusable for https sites
The page at https://myproject.com/m/map.html displayed insecure content from
http://maps.gstatic.com/intl/en_us/mapfiles/iw_close.gif.
Original comment by franci...@gmail.com
on 17 Mar 2013 at 5:25
Just had this issue ourselves.
Not only should the "HTTP:" be removed from the default 'close.src' but it
should also be an attribute that can be set by the developer via the options
when creating an instance.
Original comment by chaegrib...@gmail.com
on 2 May 2013 at 1:14
We are having the same issue. Could anyone help correcting this problem
locally?
Original comment by duke...@gmail.com
on 30 Oct 2013 at 1:33
We have the same Problem. Is there a workaround or a solution in near future?
Original comment by linxp...@gmail.com
on 15 Jan 2014 at 9:22
Yes same here (sorry for the +1)
Is infoBubble a "mature" product or still being supported.
Do we have to take a copy and modify it ourselves?
Original comment by mahe...@googlemail.com
on 29 May 2014 at 11:11
you can change the line
close.src = 'http://maps.gstatic.com/intl/en_us/mapfiles/iw_close.gif';
to
close.src = 'https://maps.gstatic.com/intl/en_us/mapfiles/iw_close.gif';
and that should solve your problem.
Original comment by JeremyPa...@gmail.com
on 26 Aug 2014 at 3:27
I have just fixed this myself after wasting a few hours finding the cause.
Why is this issue not being fixed at source?
Please just change 'http' to 'https' on line 200!
Original comment by markbanf@gmail.com
on 27 Jan 2015 at 3:03
Original issue reported on code.google.com by
johannes...@knallgrau.at
on 6 Jul 2012 at 3:02