25912 2014-05-29 09:10:30 +0000 DOMException.prototype.message is up to implementations 2014-09-26 18:22:49 +0000 1 1 1 Unclassified Web Cryptography Web Cryptography API Document unspecified PC All RESOLVED FIXED P2 normal --- 1 annevk watsonm public-webcrypto watsonm oldest_to_newest 106973 0 annevk 2014-05-29 09:10:30 +0000 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/ 106989 1 sleevi 2014-05-29 17:01:05 +0000 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. 106990 2 annevk 2014-05-29 17:40:45 +0000 Confirmed. 112296 3 watsonm 2014-09-26 18:22:49 +0000 https://dvcs.w3.org/hg/webcrypto-api/rev/52cea848d2e6