Bug 62039
| Summary: | CustomEvent interface not exposed on view | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eli Grey (:sephr) <bugmail> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | aestes, ap, cshu, kenneth, laszlo.gombos, tonikitoo |
| Priority: | P3 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Eli Grey (:sephr)
The CustomEvent interface should be exposed on the view, like Event, UIEvent, etc.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Kenneth Rohde Christiansen
Do you have a lionk to the spec that says it has to be exposed on the view?
Eli Grey (:sephr)
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) { ... }).
Alexey Proskuryakov
<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.
Kenneth Rohde Christiansen
OK, great. Thanks for the explanation.
Alexey Proskuryakov
This got fixed yesterday.
*** This bug has been marked as a duplicate of bug 67248 ***