I've been confused about this before too, and I think the current text is fine as-is.

The constructor algorithm is actually specified in the DOM spec:

When a constructor of the Event interface, or of an interface that inherits from the Event interface, is invoked, these steps must be run, given the arguments type and eventInitDict:

Let event be the result of running the inner event creation steps with this interface, null, now, and eventInitDict.

Initialize event’s type attribute to type.

Return event.

which also takes care of initializing the error attribute.

As for the description of the attribute itself, I'm following the style used by the WHATWG specs as well as e.g. AppHistory:

https://dom.spec.whatwg.org/#dom-event-type
https://websockets.spec.whatwg.org/#dom-closeevent-wasclean
https://wicg.github.io/app-history/#dom-apphistorynavigateevent-cantransition

@domenic is this the recommended style or is it better to have internal slots for the attributes and follow the more usual "the error getter steps are to return [=this=].[[Error]]" path?

Properly specify the constructor algorithm and internal slots for SensorErrorEvent #426

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions