* Anne van Kesteren wrote:
I think you saw that we changed this to be more compatible with Internet
Explorer. Basically, from the window you contruct the object in you take
the window.document.baseURI property and somehow store that on the object
to resolve URIs against.
The specification
On Wed, 27 Sep 2006 22:12:18 +0200, Boris Zbarsky [EMAIL PROTECTED] wrote:
Bjoern Hoehrmann wrote:
* the internal [[Construct]] method must determine and memorize the
/XHR base resource identifier reference/, the value of the baseURI
property of the document property of the global
* Boris Zbarsky wrote:
Bjoern Hoehrmann wrote:
* the internal [[Construct]] method must determine and memorize the
/XHR base resource identifier reference/, the value of the baseURI
property of the document property of the global object associated
with the caller of the method
On Wed, 27 Sep 2006 23:01:42 +0200, Bjoern Hoehrmann [EMAIL PROTECTED]
wrote:
I don't see what's unclear here. When [[Construct]] is called, that is
the result of evaluating a new expression. The expression is part of
one ECMAScript program. Each ECMAScript program has one global object
On Tue, 26 Sep 2006 16:37:12 +0200, Boris Zbarsky [EMAIL PROTECTED] wrote:
Again, my real issue is that the attempt at definition that currently
exists in the XMLHttpRequest spec doesn't make it clear what the terms
it's using mean.
Do you have any suggestions to improve it? I don't really
Maciej Stachowiak wrote:
You can't use apply with new. What part of the spec says you can?
I haven't been able to find the part of the spec that addresses this at all. So
the question could also be posed as What part of the spec says you can't? And
apply is just an example; I don't know
Maciej Stachowiak wrote:
I agree the definition should be clear, I'll try to review the existing
one and suggest more precise wording if needed.
Awesome. Thanks!
-Boris
Anne van Kesteren wrote:
How is that defined? Is it possible to take window1.XMLHttpRequest
and use apply() to call it with window2 as |this|?
...
Sorry, it's the window from which you use the constructor.
That doesn't answer my question above. It just shifts the burden onto defining
On Fri, 22 Sep 2006 16:41:12 -, Boris Zbarsky [EMAIL PROTECTED] wrote:
That doesn't answer my question above. It just shifts the burden onto
defining what the window from which you use the constructor means.
Can you point out the problem in that definition?
Could we have a definition
Anne van Kesteren wrote:
On Fri, 22 Sep 2006 16:41:12 -, Boris Zbarsky [EMAIL PROTECTED] wrote:
That doesn't answer my question above. It just shifts the burden onto
defining what the window from which you use the constructor means.
Can you point out the problem in that definition?
Boris Zbarsky [EMAIL PROTECTED]
To repeat it a third time. If do something along the lines of:
var func = window1.XMLHttpRequest;
var req = new (func.apply(window2)();
or some such, which is the window from which you use the constructor?
window1 or window2?
If what I said is not possible
Jim Ley wrote:
It's a host object the apply is undefined in ECMA, so I see no reason
for the WEB API's WG to define it more than ECMA does.
Unless you want better interoperability than ECMA provides, of course. Which I
do.
I would encourage you to simply not support apply on such host
On Fri, 21 Apr 2006 22:35:02 -, Boris Zbarsky [EMAIL PROTECTED] wrote:
If I follow correctly, relative URIs passed to open() should be resolved
relative to caller (whatever that means; more on that in a separate
mail). That's not actually precisely what Gecko does right now; probably
a
Anne van Kesteren wrote:
Basically, from the window you contruct the object in
How is that defined? Is it possible to take window1.XMLHttpRequest and use
apply() to call it with window2 as |this|? In that case, which window was the
object constructed in? Or is the window you construct
14 matches
Mail list logo
