ISSUE-75: Document pointer needs fixing
Document pointer needs fixing
- State:
- CLOSED
- Product:
- XHR
- Raised by:
- Anne van Kesteren
- Opened on:
- 2008-09-26
- Description:
- In the following scenarios it's not clear what should happen to the Document pointer:
var randomObj = {};
randomObj.XMLHttpRequest = someWindow.XMLHttpRequest;
new randomObj.XMLHttpRequest();
or
window.foreignXHR = otherWindow.XMLHttpRequest
new foreignXHR();
Needs testing in Internet Explorer since we followed that for the definition of Document pointer so far. (Thanks to Sam and Maciej.) - Related Actions Items:
- No related actions
- Related emails:
- ISSUE-75 and ISSUE-91: closing (from annevk@opera.com on 2009-09-25)
- Re: Next steps for XHR L1 spec? (from annevk@opera.com on 2009-05-04)
- Re: ISSUE-75: Document pointer needs fixing [XHR] (from annevk@opera.com on 2009-01-07)
- ISSUE-75: Document pointer needs fixing [XHR] (from sysbot+tracker@w3.org on 2008-09-26)
Related notes:
Lets assume I fixed this and see what breaks.
Anne van Kesteren, 25 Sep 2009, 12:23:04Actually closing this time.
Anne van Kesteren, 25 Sep 2009, 12:27:35Display change log
