Closed Bug 229294 Opened 17 years ago Closed 4 years ago
Request - doesn't calculate base URI correctly (scriptcontext?)
I meant XML, sorry.
Component: Web Services → XML
Putting some printfs confirms that GetDocumentFromScriptContext() returns the document from page B.
15 years ago
Yes, this is exactly what is happening. Are you sure that is "wrong" though? I.e, what does IE do?
Note that I raised this with the web apis WG today.
IE(In reply to comment #3) > Yes, this is exactly what is happening. Are you sure that is "wrong" though? > I.e, what does IE do? > Tested this on IE, it does not produce the same bug (i.e. uses URL from page A). This can be worked around in FF by having page A use window.setTimeout to execute the function (found workaround at http://dema.ruby.com.br/articles/2005/05/06/be-careful-when-mixing-ajax-and-popup-windows-on-firefox).
I believe we've decided that the W3C spec will define more or less IEs behaviour as the correct one, so keeping this bug open to make us conform with the spec once the spec is out.
I will wait a patch.
Windows Vista, Firefox 126.96.36.199
Note that the specification now defines this. http://tc.labs.opera.com/apis/XMLHttpRequest/open/ has a bunch of related testcases.
Assignee: web-services → nobody
QA Contact: doronr → xml
I can't reproduce this problem. In particular, http://web.mit.edu/bzbarsky/www/testcases/xmlhttprequest/base-uri-1.html shows that we use the base URI of the callee here, as do WebKit and Blink.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.