- From: Edgar Chen <notifications@github.com>
- Date: Fri, 20 Mar 2020 18:11:18 -0700
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 21 March 2020 01:11:30 UTC
EdgarChen commented on this pull request. > @@ -10722,6 +10654,64 @@ for the specific requirements that the use of </div> +<h4 oldids="dom-unrestricteddouble dom-unrestrictedfloat idl-unrestricted-double idl-unrestricted-float" + id="Unrestricted" extended-attribute lt="Unrestricted">[Unrestricted]</h5> + +If the [{{Unrestricted}}] [=extended attribute=] appears on one of the [=float types=], +it creates a new IDL type such that that when an ECMAScript Number is converted to the IDL type, +IEEE 754 non-finite, and special "not a number" values (NaNs) are allowed. [[!IEEE-754]] + +The [{{Unrestricted}}] +extended attribute must +[=takes no arguments|take no arguments=]. + +A type annotated with the [{{Unrestricted}}] extended attribute must not appear +in a [=read only=] attribute. A type that is not a [=float type=] must not Is there any reason we don't allow `[Unrestricted]` appeared in a read only attribute? There is such usage in current spec, like https://html.spec.whatwg.org/multipage/media.html#htmlmediaelement -- 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/pull/857#pullrequestreview-378878478
Received on Saturday, 21 March 2020 01:11:30 UTC