Bug 62039 - CustomEvent interface not exposed on view
Summary: CustomEvent interface not exposed on view
Status: RESOLVED DUPLICATE of bug 67248
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P3 Normal
Assignee: Nobody
Depends on:
Reported: 2011-06-03 12:29 PDT by Eli Grey (:sephr)
Modified: 2011-08-31 10:23 PDT (History)
6 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Eli Grey (:sephr) 2011-06-03 12:29:12 PDT
The CustomEvent interface should be exposed on the view, like Event, UIEvent, etc.
Comment 1 Kenneth Rohde Christiansen 2011-06-05 08:47:35 PDT
Do you have a lionk to the spec that says it has to be exposed on the view?
Comment 2 Eli Grey (:sephr) 2011-06-05 11:37:41 PDT
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) { ... }).
Comment 3 Alexey Proskuryakov 2011-06-05 13:05:33 PDT
<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.
Comment 4 Kenneth Rohde Christiansen 2011-06-05 13:14:31 PDT
OK, great. Thanks for the explanation.
Comment 5 Alexey Proskuryakov 2011-08-31 10:23:20 PDT
This got fixed yesterday.

*** This bug has been marked as a duplicate of bug 67248 ***