infoBox won't work in IE 8

GeoffSchultz

unread,

Nov 30, 2011, 6:22:58 PM11/30/11

to google-maps-utility-library-v3

I'm having a problem with getting infoBox to work with IE 8. With IE
8 all that I see is the [X] close box. It works fine with Firefox,
Chrome, Safari. This is a very simple example.

http://www.geoffschultz.org/Test/infobox.html

Unfortunately I've based a much larger project on infoBox and I'd hate
to have to redo it. Any help would be GREATLY appreciated.

-- Geoff

鹏李

unread,

Dec 1, 2011, 3:34:17 AM12/1/11

to google-maps-uti...@googlegroups.com

you example is work with my IE 8. Hello World! is shown.

2011/11/30 GeoffSchultz <geoffrey....@gmail.com>

--
You received this message because you are subscribed to the Google Groups "google-maps-utility-library-v3" group.
To post to this group, send email to google-maps-uti...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-utility-l...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-utility-library-v3?hl=en.

GeoffSchultz

unread,

Dec 1, 2011, 6:01:49 AM12/1/11

to google-maps-utility-library-v3

Stupid me...It works in IE 8 but NOT in IE 9. I'm getting confused
with all of the various browsers that I've checked.

-- Geoff

Gary Little

unread,

Dec 1, 2011, 5:19:22 PM12/1/11

to google-maps-utility-library-v3

You seem to have commented out the line that includes the infobox.js
library. Try removing the // and try again. Also make sure you're
using the latest version 1.1.9.

Gary

Gary Little

unread,

Dec 1, 2011, 6:50:49 PM12/1/11

to google-maps-utility-library-v3

Sorry, my mistake, the <script> line, of course, is not commented out
because // only comments out Javascript!

However, please be sure to use the latest version 1.1.9 to see if it
makes a difference. I've tried some other InfoBoxes with IE 9 today
and everything worked, so not sure what's going on.

Gary

GeoffSchultz

unread,

Dec 2, 2011, 7:30:24 AM12/2/11

to google-maps-utility-library-v3

I seem to have been running V1.0. I can't imagine how I got that
version as I got it within the last few weeks.

Anyhow, I switched to 1.1.9 and that solved the problem along with
several others that I had to implement work-arounds for. Thanks so
very much for the suggestion as I had checked the on-line version just
a few days ago and saw that it was from early October and I knew that
I had grabbed it after that.

Now I have to remove some of my work-arounds, but that's a LOT easier
than dealing with things that I couldn't understand.

-- Geoff

Reply all

Reply to author

Forward