- From: Domenic Denicola <notifications@github.com>
- Date: Wed, 10 May 2017 11:41:42 -0700
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 10 May 2017 18:42:15 UTC
I don't understand this, especially the claim that EnforceRange is not testable or can throw any error. Its behavior is normatively specified: > See the rules for converting ECMAScript values to the various IDL integer types in ยง3.2 ECMAScript type mapping for the specific requirements that the use of [EnforceRange] entails. leads to https://heycam.github.io/webidl/#abstract-opdef-converttoint > If the conversion is to an IDL type associated with the [EnforceRange] extended attribute, then: which throws a TypeError. Is this a change request to change it to RangeError? If so we can see if any implementers are interested in changing, but going from 4 interoperable implementations of the spec to 0 is not generally a popular move. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/heycam/webidl/issues/359#issuecomment-300576009
Received on Wednesday, 10 May 2017 18:42:15 UTC