«

In document "A.html" I have defined a function and within the document
body have included an IFRAME element who's source is document "B.html".
In document "B.html" I am trying to call the function defined in
"A.html", but every attempt results in an "is not a function" error. I
have tried to invoke the function using parent.document.funcname(),
top.document.funcname(), and various other identifying methods, but all
result in the above error. Any pointers would be greatly appreciated!

Example code, document "A.html":

<script>
function foo()
{
alert("foo!");
}
</script>
....
<IFRAME src="B.html">No frames?</IFRAME>

Example code, document "B.html":
<script>
parent.document.foo();
// also tried... top.document.foo();
</script>

Thanks in advance!
-Dave H.

Try putting the call to foo in the iframe's body.onload event, and call
it with
top.foo() or parent.foo()

HTH

That worked, thanks! Actually I didn't even need to put it in the
onload event; just calling it as top.foo() rather than
top.document.foo() did the trick.

Thanks very much for the quick response!!

-Dave H.

"Dave Hammond" wrote
>
> parent.document.foo();
> // also tried... top.document.foo();

Functions are not properties of the document, but of the window.
Try
parent.foo();
or
top.foo();

You may want to perform some checks first:
if( parent.foo ) { // function exists, so go ahead
parent.foo();
}

Still a nasty error may occur if the parent is not in the same domain as
your iframe'd page, for example if your page is among Google Images results,
it will be loaded in a frame with a different host, and accessing any
property of parent will break the script, unless you wrap the code in a
try/catch block. It is therefore usually safer to put your scripts in the
top-document, and copy the necessary parts to the iframe onload.

hth
ivo
http://4umi.com/web/javascript/

What's especially neat is that you can assign a new function to the top
window from the iframe, then load another document in the iframe, and
the top window's new function is still available.

Razzbar wrote:
> What's especially neat is that you can assign a new function to the top
> window from the iframe, then load another document in the iframe, and
> the top window's new function is still available.

If I'm right, I believe that's because functions are primitive data
types in JS, like strings and numbers, so they're passed "by value" in
all operations, and not by reference.

So you're really ending up with a copy of the function, the same way
you would end up with a copy of a string or a number.

Granted, functions are *way* more useful to pass around this way than
strings or numbers.

Christopher J. Hahn wrote:
> Razzbar wrote:
>> What's especially neat is that you can assign a new
>> function to the top window from the iframe, then load
>> another document in the iframe, and the top window's
>> new function is still available.
>
> If I'm right, I believe that's because functions are
> primitive data types in JS, like strings and numbers,

Functions are object in javascript. And like all other objects they can
have named properties added to them, and assigned values, at any time.

> so they're passed "by value" in all operations, and
> not by reference.
<snip>

Being objects they are passed by reference only.

Richard.

Richard Cornford wrote:
> Christopher J. Hahn wrote:
> > Razzbar wrote:
> >> What's especially neat is that you can assign a new
> >> function to the top window from the iframe, then load
> >> another document in the iframe, and the top window's
> >> new function is still available.
> >
> > If I'm right, I believe that's because functions are
> > primitive data types in JS, like strings and numbers,
>
> Functions are object in javascript. And like all other objects they can
> have named properties added to them, and assigned values, at any time.
>
> > so they're passed "by value" in all operations, and
> > not by reference.
> <snip>
>
> Being objects they are passed by reference only.
>
> Richard.

Not to be argumentative, but if they are passed by reference only then
could you explain why the referant isn't freed, causing an error in the
case described by Razzbar?

I've been too busy to actually test the case, mind you, but I'm fairly
sure he's correct.

Christopher J. Hahn wrote:


>>>Razzbar wrote:
>>>
>>>>What's especially neat is that you can assign a new
>>>>function to the top window from the iframe, then load
>>>>another document in the iframe, and the top window's
>>>>new function is still available.

> Not to be argumentative, but if they are passed by reference only then
> could you explain why the referant isn't freed, causing an error in the
> case described by Razzbar?

What does pass by reference or value have to do with the case of frames?
If you have a global variable in one frame then it is a property of the
window object of the frame thus if the iframe document does
parent.varName = someExpression
then a global variable in the parent window is set and that variable
does not change if a new document is loaded into the iframe as the
iframe has its own window object with its own variables.
Whether that expression evaluates to a primitive value or a function
object does not matter at all, there is not even a method or function
with arguments involved where the term passing by reference or value
makes sense.

--

Martin Honnen
http://JavaScript.FAQTs.com/

Martin Honnen wrote:
> Christopher J. Hahn wrote:
>
>
> >>>Razzbar wrote:
> >>>
> >>>>What's especially neat is that you can assign a new
> >>>>function to the top window from the iframe, then load
> >>>>another document in the iframe, and the top window's
> >>>>new function is still available.
>
> > Not to be argumentative, but if they are passed by reference only then
> > could you explain why the referant isn't freed, causing an error in the
> > case described by Razzbar?
>
> What does pass by reference or value have to do with the case of frames?

Assign an object created in a child frame to a property of the parent
window, then navigate away from that document in the child frame and
attempt to manipulate the object in the parent window, and then maybe
you can tell me.
"Can't execute code from a free script."

> If you have a global variable in one frame then it is a property of the
> window object of the frame thus if the iframe document does
> parent.varName = someExpression
> then a global variable in the parent window is set and that variable
> does not change if a new document is loaded into the iframe as the
> iframe has its own window object with its own variables.

True, but if the variable is set as a reference (i.e. the object is
passed by reference to the assignment operator) then upon navigation of
the frame the referrant will been freed and the reference broken. In my
experience, further attempts to manipulate that object will result in
the error (in IE at least):
"Can't execute code from a freed script."

Try it out, as above.

This does not appear to be the case with functions or primitive values.

> Whether that expression evaluates to a primitive value or a function
> object does not matter at all, there is not even a method or function
> with arguments involved where the term passing by reference or value
> makes sense.

It is a function of operators that they receive values of some kind,
whether they be primitive values or references to objects (see also the
statement: ;+; ). I have commonly seen this provision of values to an
operator referred to as "passing". You might call it something else. It
makes no difference.


>
> --
>
> Martin Honnen
> http://JavaScript.FAQTs.com/