17268 2012-05-31 10:54:00 +0000 Make createEvent only support the legacy interfaces 2016-02-25 21:57:26 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC All RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=103423 https://bugzilla.mozilla.org/show_bug.cgi?id=1251198 P2 normal --- 1 zcorpan annevk bugs jonas mike Ms2ger odinho w3bugs www-dom public-webapps-bugzilla oldest_to_newest 68391 0 zcorpan 2012-05-31 10:54:00 +0000 [[ If eventInterfaceName is not an ASCII case-insensitive match for "event" or for the name of an interface that inherits from the Event interface and is supported by the user agent, throw a "NotSupportedError" and terminate these steps. ]] Supporting interfaces that don't have init*Event seems useless. I think the spec should have a fixed list of supported interface strings (which would be the same as the interfaces that have init*Event), and let new interfaces throw NotSupportedError. 68399 1 bugs 2012-05-31 11:56:36 +0000 I support this change. 68403 2 annevk 2012-05-31 12:16:56 +0000 Any others than Event, UIEvent, and MouseEvent? We could keep listing MutationEvent but it should go away, right? 68406 3 zcorpan 2012-05-31 12:23:42 +0000 MutationEvent and MutationNameEvent, yeah, I guess, until it's clear that we can drop them. 68413 4 zcorpan 2012-05-31 12:34:29 +0000 (In reply to comment #3) > MutationEvent and MutationNameEvent, Except not MutationNameEvent since nobody seems to support it. 68426 5 bugs 2012-05-31 15:09:26 +0000 ProgressEvent? 68428 6 annevk 2012-05-31 15:18:13 +0000 (In reply to comment #5) > ProgressEvent? Does not have initProgressEvent(). 68505 7 annevk 2012-06-01 12:33:17 +0000 https://bitbucket.org/ms2ger/dom-core/changeset/24e237f168a0