This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25912 - DOMException.prototype.message is up to implementations
Summary: DOMException.prototype.message is up to implementations
Status: RESOLVED FIXED
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Mark Watson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-29 09:10 UTC by Anne
Modified: 2014-09-26 18:22 UTC (History)
2 users (show)

See Also:

Attachments

Description Anne 2014-05-29 09:10:30 UTC 
You cannot make normative requirements with regards to the message field of the DOMException class. This should be clear from reading http://dom.spec.whatwg.org/
Comment 1 Ryan Sleevi 2014-05-29 17:01:05 UTC 
To confirm, you're talking about "Section 14.4: Exceptions"

I agree, there's an inconsistency in the spec in that. In the tables, Message is clearly noted as optional (for the reasons you discuss). However, it appears the language "return an error" imposes a normative requirement to include the message, when there shouldn't be.
Comment 2 Anne 2014-05-29 17:40:45 UTC 
Confirmed.