ISSUE-121 - Public View
Should we note version of XHR Object
- State:
- OPEN
- Product:
- XMLHttpRequest
- Raised by:
- Sunava Dutta
- Opened on:
- 2007-10-28
- Description:
In http://lists.w3.org/Archives/Public/public-webapi/2007Sep/0043.html Sunava writes * The current draft introduces new entities to the object. We're ok with creating a new object (or versioned XHR object) in order to ensure that the standards can advance. However, a vast majority of developers will not be able to reliably use this as the millions of pages build around current IE XHR will not support them. This consequently will be a adoption blocker for the standard. o Ensure all new entities like constants, flags etc are versioned or in a new object.
- Related emails:
- ISSUE-121: Should we note version of XHR Object (from dean+cgi@w3.org on 2007-10-28)
- Re: ISSUE-120: Make XHR spec less detailed/granular (from annevk@opera.com on 2007-10-28)
Note: Some of these links may be accessible only to W3C Members.
Related notes:
2007-10-28: Jon Ferraiolo seems to support the idea in http://lists.w3.org/Archives/Public/ public-webapi/2007Sep/0044.html and the thread following, noting that XHR is generally used with wrapper functions already and asking that any versioning mechanism support this usage