So it turns out DOMException.DATA_CLONE_ERR isn't defined...
Attachment #506484 - Flags: review?(jst)
Comment on attachment 506484 [details] [diff] [review] Patch v1 >diff --git a/dom/interfaces/core/nsIDOMDOMException.idl b/dom/interfaces/core/nsIDOMDOMException.idl >--- a/dom/interfaces/core/nsIDOMDOMException.idl >+++ b/dom/interfaces/core/nsIDOMDOMException.idl >@@ -73,12 +73,13 @@ interface nsIDOMDOMException : nsISuppor > // Introduced in DOM Level 2: > const unsigned short NAMESPACE_ERR = 14; > // Introduced in DOM Level 2: > const unsigned short INVALID_ACCESS_ERR = 15; > // Introduced in DOM Level 3: > const unsigned short VALIDATION_ERR = 16; > // Introduced in DOM Level 3: > const unsigned short TYPE_MISMATCH_ERR = 17; >+ const unsigned short DATA_CLONE_ERR = 25; > > readonly attribute unsigned long code; > }; Shouldn't you update the UUID?
Comment on attachment 506484 [details] [diff] [review] Patch v1 I don't think we need to change the UUID here, this is a binary compatible change, but users of this will need to recompile if they actually use this removed constant. Either way, this is material for post 2.0...
Attachment #506484 - Flags: review?(jst) → review+
Depends on: post2.0
Whiteboard: [needs review] → [needs landing]
Whiteboard: [needs landing] → [needs landing][post-2.0]
Target Milestone: mozilla2.0 → Future
The future is now.
Whiteboard: [needs landing][post-2.0]
Target Milestone: Future → mozilla2.2
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.