62039 2011-06-03 12:29:12 -0700 CustomEvent interface not exposed on view 2011-08-31 10:23:20 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) All All RESOLVED DUPLICATE 67248 P3 Normal --- 1 bugmail webkit-unassigned aestes ap cshu kenneth laszlo.gombos tonikitoo oldest_to_newest 415091 0 bugmail 2011-06-03 12:29:12 -0700 The CustomEvent interface should be exposed on the view, like Event, UIEvent, etc. 415601 1 kenneth 2011-06-05 08:47:35 -0700 Do you have a lionk to the spec that says it has to be exposed on the view? 415631 2 bugmail 2011-06-05 11:37:41 -0700 No, it's not part of a spec, it's part of the de-facto standard of exposing most DOM interfaces so people can extend them for things such as implementing features for compatibility with future APIs and to use for feature detection, in the case of events (if (self.CustomEvent) { ... }). 415644 3 ap 2011-06-05 13:05:33 -0700 <http://www.w3.org/TR/2011/WD-DOM-Level-3-Events-20110531/#webidl-events-CustomEvent> doesn't have a [NoInterfaceObject] attribute, which per WebIDL spec means that the interface object should be exposed on the global object. This is in an informative part of the spec, and I don't know if there is anything normative, but we certainly follow the practice of exposing interface objects on DOMWindow in general. 415649 4 kenneth 2011-06-05 13:14:31 -0700 OK, great. Thanks for the explanation. 459699 5 ap 2011-08-31 10:23:20 -0700 This got fixed yesterday. *** This bug has been marked as a duplicate of bug 67248 ***