28327 2015-03-24 19:46:11 +0000 <canvas>: CanvasRenderingContext2D.putImageData cannot throw a NotSupportedError exception under ECMAScript binding *even if* any of the arguments are not finite. 2016-01-24 06:16:18 +0000 1 1 1 Unclassified WHATWG HTML unspecified All All RESOLVED MOVED https://html.spec.whatwg.org/multipage/scripting.html#pixel-manipulation P2 normal Unsorted 28064 1 saneyuki.s.snyk ian annevk contributor d mike contributor oldest_to_newest 118915 0 saneyuki.s.snyk 2015-03-24 19:46:11 +0000 # related specs - CanvasRenderingContext2D - https://html.spec.whatwg.org/multipage/scripting.html#canvasrenderingcontext2d - https://html.spec.whatwg.org/multipage/scripting.html#pixel-manipulation - WebIDL - http://heycam.github.io/webidl/#es-double # description 1. `CanvasRenderingContext2D.putImageData` says that to throw a NotSupportedError exception if any of the arguments are not finite, and the methods takes `double` as its arguments. 2. On the other hand, by WebIDL spec, `double` value type raises `TypeError` if the value is not finite when conversioning from ECMAScript to IDL Value. 3. By the above, `CanvasRenderingContext2D.putImageData` cannot throw a `NotSupportedError` because WebIDL conversion steps will raise a `TypeError` before arguments are passed to `CanvasRenderingContext2D.putImageData`, if values of arguments are not finite. 4. I found the same spec issue with "HTML Canvas 2D Context Editor's Draft 13 November 2014": http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas_CR/#dom-context-2d-putimagedata 122865 1 annevk 2015-08-28 16:03:21 +0000 Thank for reporting this, do you know what implementations do? 123161 2 d 2015-09-10 20:18:22 +0000 Firefox and Chrome do TypeError. Edge does NotSupportedError. Seems best to go with TypeError. Will PR. 123162 3 d 2015-09-10 20:24:31 +0000 https://github.com/whatwg/html/pull/133 124701 4 d 2016-01-24 06:16:18 +0000 *** Bug 28064 has been marked as a duplicate of this bug. ***