Closed GoogleCodeExporter closed 9 years ago
Nice app!
So I'm wondering which poly its talking about? I wish there were a line number
in
the script! It might be the rectangle around the biodiesel grade (unless that
is just
an HTML border).
Would you mind sharing the code that went into the body of the info window? Or
even
better paring down the code to a place that generates this error and posting
that?
Original comment by galgwt.reviews@gmail.com
on 2 Jun 2008 at 10:33
Attachments:
According to Firebug, the only <area> tags in my app are in this element:
<map id="iwMap0" name="iwMap0"><area shape="poly" href="javascript:void(0)"
coords="0,0,0,179,221,179,172,250,266,179,433,179,433,0"/><area shape="poly"
href="javascript:void(0)" coords=""/><area shape="poly"
href="javascript:void(0)"
coords=""/><area shape="poly" href="javascript:void(0)"
coords="230,149,227,150,225,151,223,153,221,157,221,161,222,163,223,165,226,168,
228,172,229,175,230,179,230,183,232,183,232,179,233,175,234,173,235,170,237,167,
239,165,241,161,241,157,239,153,237,151,236,150,234,149"/><area
shape="poly" href="javascript:void(0)" coords=""/><area shape="poly"
href="javascript:void(0)" coords=""/><area shape="poly"
href="javascript:void(0)"
coords=""/><area shape="poly" href="javascript:void(0)" coords=""/><area
shape="poly"
href="javascript:void(0)" coords=""/></map>
I think this may have to do with a the custom map control I added, called
"Legend".
Original comment by ebesse...@gmail.com
on 2 Jun 2008 at 1:39
This looks to be either a Firebug or Google Maps API problem. I did find this
thread,
http://groups.google.com/group/Google-Maps-API/browse_frm/thread/abd9113f48865fd
d/c1fa732f972b860d?lnk=gst&q=coords+area#,
but it talks about version 1 of the maps API and I'm using version 2.
Original comment by ebesse...@gmail.com
on 2 Jun 2008 at 1:43
Oh, and here's the html inside the window:
<div class="bm-info_window">
<div class="bm-info_title">Quality Auto Service</div>
<div class="bm-info_type">B99</div>
<div class="bm-info_contact">
<a href="mailto:steverecchi@mac.com" class="bm-info">Steve Recchi</a>
</div>
<div class="bm-info_phone">206-780-8088</div>
<div class="bm-info_links">
<a onclick="JavaScript: window.openDirections( '220 Olympic Drive SE,Bainbridge
Island, WA 98110, US' );" class="bm-info" href="JavaScript: void( 0 );">
Directions
</a>
<br/>
<a onclick="JavaScript: window.centerAndZoomToCurrentLocation(47.623752,
-122.512635)" class="bm-info" href="JavaScript: void( 0 );">
Center and Zoom
</a>
</div>
<div class="bm-info_address">220 Olympic Drive SE<br/>Bainbridge Island, WA 98110,
US<div id="distance"/>
<hr class="bm-info"/>
<div class="bm-info_notes">all major credit cards....</div>
</div>
</div>
</div>
</div>
The more I look at this, the more I think it has something to do with my links
inside
the Info Window and Google Maps trying to do something special with them. I'll
move
this over the Google Maps API Group.
Thanks for the quick reply.
Original comment by ebesse...@gmail.com
on 2 Jun 2008 at 1:55
Now I'm thinking this may have something to do with using:
marker.openInfoWindow(node)
Instead of:
GEvent.trigger(marker, "click")
Original comment by ebesse...@gmail.com
on 2 Jun 2008 at 2:07
I revisted your site and it seems you've worked around the problem. I'm closing
this
report feel free to comment if there is something more to add.
Original comment by galgwt.reviews@gmail.com
on 4 Jun 2008 at 8:27
It's still happening for me in Firefox. Even with Firebug disabled, when I
click on
an icon to open an Info Window, the firefox.exe process goes to 98% cpu and just
continues to use more memory until I have to kill the process because it locks
my
computer.
I would think this was a programming mistake on my part, but when I view the
site in
IE7, there's no CPU or memory change after clicking on a link.
If you can think of a way that I can research this bug this better, I'd really
like
to hear it.
At this point though, I'm can't be certain if this is a Firefox, Maps API, GWT,
or
GWT Google API issue or an issue with my own code. I'm sure you have more
important
things to work on, so if I find out more info I'll post it here, but I don't
expect
you guys to look into this any more.
Thanks,
Eric
Original comment by ebesse...@gmail.com
on 5 Jun 2008 at 12:26
Original comment by zundel@google.com
on 21 Dec 2009 at 1:57
Original issue reported on code.google.com by
ebesse...@gmail.com
on 2 Jun 2008 at 6:32