by clicking on the lines on the right column, infowindow will shown
on the map.
it used to be work, the infowindows blowup/close functions had worked
ok in firefox/ie/opera before yesterday.
Now there are errors with the infowindows with firefox 2.0.0.16.
and even the maps are not shown with ie 6.0, but still all is ok in
opera.
I'm using ditu.google.com, just could not figure out what wrong,
GEvent.addListener(marker,"click",function(){
//TODO cache
GDownloadUrl("/point?operation=get&key="+key,
function(jsondata,code){
if(code==200){
var data = eval('(' + jsondata + ')');
var html = '';
html += "<ul style='width:200px;list-style:none;'>";
//blabla
html += "</ul> ";
map_.setCenter(marker.getLatLng(), 14); //move setCenter
here
//TODO cache
GDownloadUrl("/point?operation=get&key="+key,
function(jsondata,code){
if(code==200){
var data = eval('(' + jsondata + ')');
var html = '';
html += "<ul style='width:200px;list-style:none;'>";
//blabla
html += "</ul> ";
marker.openInfoWindowHtml(html);
}else{
}
});
On 7月22日, 上午9时05分, atomicBirdsong <wjam...@nyc.rr.com> wrote:
In case the programmers are reading, it's all map clicks. (This has
driven me crazy, thought I'd broken my map!) My formerly clickable
polygons now give the same Line 132 error.
> by clicking on the lines on the right column, infowindow will shown
> on the map.
> it used to be work, the infowindows blowup/close functions had worked
> ok in firefox/ie/opera before yesterday.
> Now there are errors with the infowindows with firefox 2.0.0.16.
> and even the maps are not shown with ie 6.0, but still all is ok in
> opera.
> I'm using ditu.google.com, just could not figure out what wrong,
Same problem in Firefox even when changing opts to {}, or to anything
else for that matter.
The google example http://code.google.com/apis/maps/documentation/examples/map-infowindo... worked correctly the first time around with the infoWindow displaying.
After a reload of the page however, the infoWindow has disappeared.
Even exiting Firefox and relaunching doesn't bring the infoWindow
back.
I downloaded the above example map-infowindow.html to a local file.
The infoWindow displayed correctly until I reloaded the page. Same for
http://econym.googlepages.com/example_map.htm - works fine until the
page is reloaded.
Firebug keeps complaining that 'a has no properties' main.js (line
1399).
Everything works just fine in Opera...
On Jul 22, 5:41 am, chan <leoyc...@gmail.com> wrote:
> Same problem in Firefox even when changing opts to {}, or to anything
> else for that matter.
> The google examplehttp://code.google.com/apis/maps/documentation/examples/map-infowindo...
> worked correctly the first time around with the infoWindow displaying.
> After a reload of the page however, the infoWindow has disappeared.
> Even exiting Firefox and relaunching doesn't bring the infoWindow
> back.
> I downloaded the above example map-infowindow.html to a local file.
> The infoWindow displayed correctly until I reloaded the page. Same forhttp://econym.googlepages.com/example_map.htm- works fine until the
> page is reloaded.
> Firebug keeps complaining that 'a has no properties' main.js (line
> 1399).
> Everything works just fine in Opera...
> On Jul 22, 5:41 am, chan <leoyc...@gmail.com> wrote:
> > I tried what you did and I still have the same problem.
> > On Jul 21, 9:05 pm, atomicBirdsong <wjam...@nyc.rr.com> wrote:
> > > Well the problem seems to be a new bug inopenInfoWindow( content,
> > > options )
> > > In my scripts I generally do this:
> > > var opts = null
> > > if (something){
> > > opts = {foo:bar}}
> > > Marker.openInfoWindow( somecontent, opts );
> > > when opts is null like this it is now causing an error in the google
> > > api base code.
> > > when I flipped that var opts to an empty object the error went away.
> > > var opts = {}
> > > if this is the case, passing null should be valid as it is optional
> > > according to the api. null would explain the undefined.
> Same problem in Firefox even when changing opts to {}, or to anything
> else for that matter.
> The google examplehttp://code.google.com/apis/maps/documentation/examples/map-infowindo...
> worked correctly the first time around with the infoWindow displaying.
> After a reload of the page however, the infoWindow has disappeared.
> Even exiting Firefox and relaunching doesn't bring the infoWindow
> back.
> I downloaded the above example map-infowindow.html to a local file.
> The infoWindow displayed correctly until I reloaded the page. Same forhttp://econym.googlepages.com/example_map.htm- works fine until the
> page is reloaded.
> Firebug keeps complaining that 'a has no properties' main.js (line
> 1399).
> Everything works just fine in Opera...
> On Jul 22, 5:41 am, chan <leoyc...@gmail.com> wrote:
> > I tried what you did and I still have the same problem.
> > On Jul 21, 9:05 pm, atomicBirdsong <wjam...@nyc.rr.com> wrote:
> > > Well the problem seems to be a new bug inopenInfoWindow( content,
> > > options )
> > > In my scripts I generally do this:
> > > var opts = null
> > > if (something){
> > > opts = {foo:bar}}
> > > Marker.openInfoWindow( somecontent, opts );
> > > when opts is null like this it is now causing an error in the google
> > > api base code.
> > > when I flipped that var opts to an empty object the error went away.
> > > var opts = {}
> > > if this is the case, passing null should be valid as it is optional
> > > according to the api. null would explain the undefined.