Google Layer is broken.

Will commit w/ review.

good fix but is there a reason why we are changing where the function is tagged on?

yes - extending the mapObject prototype doesn't give us access to the layer - which is what you need to traverse down the dom

all tests pass and examples work in IE/FF

note that it is different to extend the prototype and to extend an object - thus the binding

and if you're trying the same with the prototype extension - all will work fine with one GMap instance per page - but will fail with more as the layer that gets bound to the prototype method is the last layer initiatiated

use documented getContainer method

New patch, easier on the eyes, and uses a documented method!!! Thanks Uz!

sweeeeet! new patch is excellent, cuts right to the heart of the problem. tests pass in ie6, ff. please commit, mark as pullup.

note that we're going to have to produce some retroactive patch for old versions of OL so that they can still use gmaps.

also note that since we're still doing firstChild.firstChild on the the result from getContainer(), we're still technically doing a little mucking about.. and maybe it's best to put a special disclaimer about this on the google layer. or something like that. just so people aren't freaked when google pulls out the rug like this.

also note that open source development *rules*! how quickly was this bug tracked down and stomped out? wicked.

(In [4375]) Use documented getContainer method instead of chasing obfuscated properties. Note that we are still tip-toeing around the dom here assuming they won't pull a fast one on us - Google users beware (see #994). Big thanks to Uz for help sleuthing this one out.

vladimir

latest patch fixes prototype problem (previous check would always fail) pleae review

Done reviewing. All green from FF/IE. Please make it happen.

(In [4380]) test to see if 'fromLatLngToContainerPixel' is defined on the prototype, not on the class. (See #994).

r4390 closes this.