W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2013

[Bug 24072] New: Clarify handling of neutered objects

From: <bugzilla@jessica.w3.org>
Date: Thu, 12 Dec 2013 09:56:20 +0000
To: public-webapps@w3.org
Message-ID: <bug-24072-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24072

            Bug ID: 24072
           Summary: Clarify handling of neutered objects
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XHR
          Assignee: annevk@annevk.nl
          Reporter: sof@opera.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

A Blob can be transitioned to a neutered state by the close() method,

   http://dev.w3.org/2006/webapi/FileAPI/#close-method

Similarly for ArrayBufferViews, and them being neutered upon transfer.

How should XMLHttpRequest.send() and FormData.append() handle such objects?
Throw an exception, considered as "empty" objects? The relevant sections of the
XMLHttpRequest specification doesn't make this clear.

It makes some sense to have the error handling be strict and throw upon use of
these no-longer-useful objects, but perhaps that's already implicitly covered
by the spec text?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 12 December 2013 09:56:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:20 UTC