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

[Bug 8496] Shouldn't a loop in structured clone throw INVALID_STATE_ERR instead? [sp]

From: <bugzilla@wiggum.w3.org>
Date: Wed, 06 Jan 2010 08:03:36 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NSQrg-00017D-My@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8496


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-01-06 08:03:36 ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Why would INVALID_STATE_ERR be appropriate? The object isn't in an
invalid state, it's the argument that's in an invalid state.

Anyway, I picked NOT_SUPPORTED_ERR because I figured one day we might support
it.


-- 
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 Wednesday, 6 January 2010 08:03:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:09 UTC