Re: [whatwg] Methods defined for one document called after that document is no longer the one being displayed

2009-02-12 Thread Ian Hickson
On Sat, 31 Jan 2009, Boris Zbarsky wrote: Ian Hickson wrote: I haven't mentioned the 'this' behavior, so right now |this !=== window|, which breaks the invariant that there is no way to actually get hold of a reference to the Window object itself (as opposed to the outer WindowProxy

Re: [whatwg] Methods defined for one document called after that document is no longer the one being displayed

2009-02-12 Thread Jonas Sicking
On Thu, Feb 12, 2009 at 7:15 PM, Ian Hickson i...@hixie.ch wrote: On Sat, 31 Jan 2009, Boris Zbarsky wrote: Ian Hickson wrote: I haven't mentioned the 'this' behavior, so right now |this !=== window|, which breaks the invariant that there is no way to actually get hold of a reference to

Re: [whatwg] Methods defined for one document called after that document is no longer the one being displayed

2009-01-31 Thread Ian Hickson
On Wed, 24 Dec 2008, Maciej Stachowiak wrote: On Aug 5, 2008, at 2:12 AM, Ian Hickson wrote: Right now, if you navigate an iframe to a document, and take a reference to a method defined in that document, and then navigate that iframe to another document, and then call the method,

Re: [whatwg] Methods defined for one document called after that document is no longer the one being displayed

2009-01-31 Thread Boris Zbarsky
Ian Hickson wrote: I haven't mentioned the 'this' behavior, so right now |this !=== window|, which breaks the invariant that there is no way to actually get hold of a reference to the Window object itself (as opposed to the outer WindowProxy object that forwards to the inner Window object).

Re: [whatwg] Methods defined for one document called after that document is no longer the one being displayed

2009-01-04 Thread Simon Pieters
On Wed, 24 Dec 2008 21:04:33 +0100, Maciej Stachowiak m...@apple.com wrote: On Aug 5, 2008, at 2:12 AM, Ian Hickson wrote: I would like some input from browser vendors. [...] Response from one of our developers: On Thu, 01 Jan 2009 14:54:18 +0100, j...@opera.com wrote: I agree with

Re: [whatwg] Methods defined for one document called after that document is no longer the one being displayed

2008-12-24 Thread Maciej Stachowiak
On Aug 5, 2008, at 2:12 AM, Ian Hickson wrote: I would like some input from browser vendors. Right now, if you navigate an iframe to a document, and take a reference to a method defined in that document, and then navigate that iframe to another document, and then call the method, browsers

[whatwg] Methods defined for one document called after that document is no longer the one being displayed

2008-08-05 Thread Ian Hickson
I would like some input from browser vendors. Right now, if you navigate an iframe to a document, and take a reference to a method defined in that document, and then navigate that iframe to another document, and then call the method, browsers differ in what they do. There are several

Re: [whatwg] Methods defined for one document called after that document is no longer the one being displayed

2008-08-05 Thread Aaron Boodman
On Tue, Aug 5, 2008 at 1:12 AM, Ian Hickson [EMAIL PROTECTED] wrote: Right now, if you navigate an iframe to a document, and take a reference to a method defined in that document, and then navigate that iframe to another document, and then call the method, browsers differ in what they do. By

Re: [whatwg] Methods defined for one document called after that document is no longer the one being displayed

2008-08-05 Thread Ian Hickson
On Tue, 5 Aug 2008, Aaron Boodman wrote: On Tue, Aug 5, 2008 at 1:12 AM, Ian Hickson [EMAIL PROTECTED] wrote: Right now, if you navigate an iframe to a document, and take a reference to a method defined in that document, and then navigate that iframe to another document, and then call the