W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2010

[Bug 10069] New: Structured clone algorithm should throw something more informative than NOT_SUPPORTED_ERR

From: <bugzilla@jessica.w3.org>
Date: Fri, 02 Jul 2010 20:39:29 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-10069-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10069

           Summary: Structured clone algorithm should throw something more
                    informative than NOT_SUPPORTED_ERR
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: jonas@sicking.cc
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org


Currently the structured clone algorithm throws a NOT_SUPPORTED_ERR error when
the cloning fails (for example due to the cloned object containing host
objects). This is a fairly generic and uninformative error.

One problem is that this makes it hard to defer to the HTML5 spec for other
specs that are using structured clones. For example IndexedDB uses the
structured clone algorithm for the IDBObjectStore.add method. However if all
that is thrown if a "uncloneable" is passed to IDBObjectStore.add is
NOT_SUPPORTED_ERR, then that gives the author very little information about
what went wrong.

I propose we instead throw a DATA_CLONE_ERR error, or some such.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 2 July 2010 20:39:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:51 UTC