Well, I thought having the table row click handler ($('tr').live("click",
function()) inside the $(document).ready function, that it would be
listening for the click after the infowindow content is set
(infoWindow.setContent(content)). Your solution moved the table row click
handler into the domready event which I thought is basically doing the same
as $(document).ready. So if the domready listener is different than
$(document).ready, how is it different?
On Wednesday, October 10, 2012 9:43:44 AM UTC-4, [email protected] wrote:
>
> On Oct 10, 6:06 am, Quaye Trimble <[email protected]> wrote:
> > Larry - Can you explain how the domready listener is different
> > than having the click listener ready to roll once
> > infoWindow.setContent(content) is called.
>
> What do you mean by "having the click listener ready to roll once
> infoWindow.setContent(content) is called."
>
> The infoWindow is not part of the DOM until some time after the click
> listener runs, that is when the domready event fires.
>
> If you need to run code that uses the DOM to access elements, it wound
> work until after domready.
>
> -- Larry
>
>
> >
> >
> >
> >
> >
> >
> >
> > On Tuesday, October 9, 2012 10:42:29 PM UTC-4, [email protected]:
> >
> > > On Oct 9, 12:23 pm, Quaye Trimble <[email protected]> wrote:
> > > > Thanks Rossko - I just implemented my new method which is what you
> > > > described. Just a few things I still need to do. Here is the link:
> > >http://bccmws.coastal.edu/LBOOS/dev_gmap2.html. Can you not use
> > > something
> > > > like Firebug to see my code?
> >
> > > This sort of what you are trying to do?
> > >http://www.geocodezip.com/bccmws_coastal_edu_LBOOS_dev_gmap_b.html
> >
> > > Still doesn't show the very first time.
> >
> > > -- Larry
> >
> > > > On Tuesday, October 9, 2012 2:46:04 PM UTC-4, Rossko wrote:
> >
> > > > > > Is it possible to reference an HTML element that exists inside
> an
> > > info
> > > > > > window prior to the marker click event?
> >
> > > > > That would depend if the infowindow exists yet or not. That
> depends on
> > > > > your code that we can't see. Very often it doesn't exist yet.
> > > > > A workaround would be to create the HTML content in the DOM
> > > > > beforehand, and "park" it somewhere invisible. Then re-use it
> when
> > > > > you do create the infowindow.
> >
> > > > > Here's a different approach you might be able to adapt
> >
> > > > >
> http://groups.google.com/group/google-maps-js-api-v3/browse_thread/th...
> >
> > > > > which avoids requiring things before they are created.
>
--
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/-/AmrGaEMuWH8J.
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.
