This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17268 - Make createEvent only support the legacy interfaces
Summary: Make createEvent only support the legacy interfaces
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-31 10:54 UTC by Simon Pieters
Modified: 2016-02-25 21:57 UTC (History)
7 users (show)

See Also:

Attachments

Description Simon Pieters 2012-05-31 10:54:00 UTC 
[[
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.
Comment 1 Olli Pettay 2012-05-31 11:56:36 UTC 
I support this change.
Comment 2 Anne 2012-05-31 12:16:56 UTC 
Any others than Event, UIEvent, and MouseEvent? We could keep listing MutationEvent but it should go away, right?
Comment 3 Simon Pieters 2012-05-31 12:23:42 UTC 
MutationEvent and MutationNameEvent, yeah, I guess, until it's clear that we can drop them.
Comment 4 Simon Pieters 2012-05-31 12:34:29 UTC 
(In reply to comment #3)
> MutationEvent and MutationNameEvent, 

Except not MutationNameEvent since nobody seems to support it.
Comment 5 Olli Pettay 2012-05-31 15:09:26 UTC 
ProgressEvent?
Comment 6 Anne 2012-05-31 15:18:13 UTC 
(In reply to comment #5)
> ProgressEvent?

Does not have initProgressEvent().