If the div is 'printed' via PHP, then jquery will 'see' it when it
runs. If it's not 'printed', then jquery will NOT see it.
But I think your problem may be your selector. Looks like you have a
space between 'div' and '.contacts'. If you are trying to target a
div with a class of 'contacts', then you should use
'div.contacts' (no space there)
Simplest way to test this would be to put an alert() statement in your
click handler so you can see if that event is even being triggered.
Once you're sure the event is firing, then you can work on how to call
the function in the parent page. On that note, if the function DOES
exist in the parent page, my example should work. jquertil's example
was how to interact with the DOM of the parent, not how to call a
function that exists on the parent.
On Nov 6, 10:23 pm, CodingCyborg <[EMAIL PROTECTED]> wrote:
> Hmm, I think I've been attempting to solve a problem that doesn't
> exist. Or it just wasn't the only one. Currently the link in the
> iFrame is in a PHP page. I've had problems with PHP and jQuery not
> seeing each other like I had expected. jQuery isn't recognizing that
> the div exists for some reason. I'm not sure if that's because the div
> only possibly exists and is "print"ed onto the page if needed, or for
> some other reason. Is there a possible fix for helping jQuery
> recognize that the div has a function connected to it?
>
> On Nov 6, 9:58 pm, CodingCyborg <[EMAIL PROTECTED]> wrote:
>
> > I can't seem to find documentation on the additional parameters of the
> > jQuery selectors. I've searched the jQuery site and Google, but can't
> > find this information. A link to the page would be helpful.
>
> > On Nov 6, 6:25 pm, jquertil <[EMAIL PROTECTED]> wrote:
>
> > > sorry I dont really understand your question, but inter-frame actions
> > > work something like this:
>
> > > $('#button').click(function(){
> > > $("#divInParentFrame",top.document).remove();
> > > });
>
> > > read up on jquery's selectors and additional parameters, its all in
> > > the documentation. notice the comma after the element selector, that's
> > > where you address the frame to which you want to talk to
