http://www.meerijden.nu/kaltest.php is a simple test of the problem. It has to do with the calculation of the top and left offset. If you select a date you get the target name and top-offset of every parent of the date element and finaly the top and left offset of the calendar.. So you can compare this in IE and Chrome. This is the way the top offset is calculated by epoch: Epoch.prototype.getTop = function (element) //PRIVATE: returns the absolute Top value of element, in pixels { var oNode = element; var iTop = 0; while(oNode != null && oNode.tagName != 'BODY') { alert(oNode.tagName); alert(oNode.offsetTop); iTop += oNode.offsetTop; oNode = oNode.offsetParent; } return iTop; The calendar is wrong positioned in Chrome. BUT if you leave out the height parameter in the div in kaltes than it also in Chrome the positiong is good. AND if you have the same div outside an infowindow and outside the map than it functions also well. My conclusion is that it has to do with the offset calculation in an infowindow and that it is also dependent the way the date element is written in the page. I hope that this will be helpfull to come to a solution. Nico.
-- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/HDx1ish6u9oJ. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
