I seem to have pasted incorrectly, The working listener for Prototype
was actually:

google.maps.event.addListener(infowindow, 'domready', function(){
        $('infoWindow').parentNode.setStyle({
           overflow: ''
        });
        $('infoWindow').parentNode.parentNode.setStyle({
           overflow: ''
        });
    });

The listener I thought would work was:

    google.maps.event.addListener(infowindow, 'domready', function(){
        $('infoWindow').getOffsetParent().setStyle({
           overflow: ''
        });
        $
('infoWindow').getOffsetParent().getOffsetParent().setStyle({
           overflow: ''
        });
    });

Just in case someone happens to be googling for this...

On Sep 9, 5:38 pm, JoshN <[email protected]> wrote:
> Pete,
>
> Thanks for grabbing my attention, I had indeed stopped watching this
> thread, but would rather not close then reopen the infowindow.
>
> Something odd came up while applying the change.
>
> I am using prototype 1.6.1--though I usually translate back to normal
> js when posting short bits. When using the fix listed above,
> translated to prototype as:
>
>     google.maps.event.addListener(infowindow, 'domready', function()
> {
>         $('infoWindow').getOffsetParent().setStyle({
>            overflow: ''
>         });
>         $('infoWindow').getOffsetParent().setStyle({
>            overflow: ''
>         });
>     });
>
> The horizontal scrollbar remains.
>
> When I substitute parentNode for getOffsetParent() the problem
> subsides:
>
>     google.maps.event.addListener(infowindow, 'domready', function()
> {
>         $('infoWindow').parentNode.setStyle({
>            overflow: ''
>         });
>         $('infoWindow').parentNode.setStyle({
>            overflow: ''
>         });
>     });
>
> I'll try to create a simple example and see if it is a conflict with
> my own script, which is rather absurdly large.
>
> On Sep 8, 10:21 am, Peter Lawless <[email protected]> wrote:
>
>
>
> > Hi Josh
>
> > Have you seen the rest of the thread? Franky found a bug in my original
> > code, which probably explains why you were having to close and open the
> > infowindow to get the fix to work.
>
> > See the rest of the thread for the fix. Trouble is I still think in UCSD
> > Pascal where things happed in sequence!
>
> > Pete
>
> > On Tue, Sep 7, 2010 at 12:38 AM, JoshN <[email protected]> wrote:
> > > I forgot to mention that my content div's id is also infowindow, as
> > > you probably figured out..
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Google Maps JavaScript API v3" group.
> > > To post to this group, send email to
> > > [email protected].
> > > To unsubscribe from this group, send email to
> > > [email protected]<google-maps-js-api-v3%2B
> > >  [email protected]>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-maps-js-api-v3?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps JavaScript API v3" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-maps-js-api-v3?hl=en.

Reply via email to