17760 2012-07-12 15:56:19 +0000 createPattern(canvas, null) now throws rather than 'repeat' 2012-08-20 23:33:12 +0000 1 1 1 Unclassified HTML WG HTML Canvas 2D Context unspecified PC All CLOSED FIXED P2 normal --- 17891 1 krisk cabanier cabanier ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 69889 0 krisk 2012-07-12 15:56:19 +0000 For compatibility and interoperability it would seem far safer to not throw an exception when createPattern(canvas, null) is used. In the below list of browsers that treat this as a 'repeat' e.g. createPattern(canvas, 'repeat'). The previous version of the spec had a normative statement that matched the majority of browsers. The latest version of the spec changed this normative statement. Previous Spec 'If the empty string or null is specified, repeat must be assumed. If an unrecognized value is given, then the user agent must raise a SYNTAX_ERR exception' Current working draft has changed to 'If the empty string is specified, repeat must be assumed. If an unrecognized value is given, then the user agent must raise a SYNTAX_ERR exception.' Treats null as 'repeat' Firefox 13.1 Internet Explorer 9 Chrome 20 Opera 12 does indeed raise an exception when passed 'null' Test Case http://www.w3c-test.org/html/tests/submission/PhilipTaylor/canvas/2d.pattern.repeat.null.html Related Bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=17141 70046 1 Ms2ger 2012-07-17 15:32:52 +0000 Nightly also throws. 70253 2 contributor 2012-07-18 07:13:14 +0000 This bug was cloned to create bug 17891 as part of operation convergence. 72217 3 Ms2ger 2012-08-15 17:13:19 +0000 Filter on [Idon'tcareaboutHTMLWGbugspam]. 72249 4 cabanier 2012-08-15 17:29:02 +0000 This was a result of an update to the IDL, see: https://www.w3.org/Bugs/Public/show_bug.cgi?id=10640 I'm unsure if this was an intended change. Pinged the writer of the patch. 72266 5 cabanier 2012-08-16 00:58:10 +0000 (In reply to comment #4) > This was a result of an update to the IDL, see: > https://www.w3.org/Bugs/Public/show_bug.cgi?id=10640 > > I'm unsure if this was an intended change. Pinged the writer of the patch. Cameron McCormack says that this was an accidental change. This should be reverted to the previous behavior. 72449 6 cabanier 2012-08-20 21:45:52 +0000 Fixed. https://github.com/w3c/html/commit/0bb4926b0be517ff9cf5bff835dcf293966350d8 72458 7 ian 2012-08-20 23:33:12 +0000 (Please note that the WHATWG spec will not be taking this change, as it does not lead towards interop and is a technically worse state for the spec to be in.)