Skip to content

Commit 61ce33d

Browse files
author
Raphael Kubo da Costa
committed
Improve SensorErrorEvent description.
Related to #426. - Refer to Event's constructor steps to describe how SensorErrorEvent is initialized and avoid confusion in the future. - Instead of having a separate session for SensorErrorEvent.error, just have a paragraph with the kind of boilerplate description that specs like DOM, WebSockets and App History.
1 parent 1919432 commit 61ce33d

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

index.bs

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1239,12 +1239,12 @@ dictionary SensorErrorEventInit : EventInit {
12391239
};
12401240
</pre>
12411241

1242+
{{SensorErrorEvent}} instances are constructed by following the steps described
1243+
in {{Event}}'s <a for="Event">constructor</a>.
12421244

1243-
### SensorErrorEvent.error ### {#sensor-error-event-error}
1244-
1245-
The {{SensorErrorEvent/error!!attribute}} getter steps are to return the value it was initialized to.
1246-
1247-
It represents the {{DOMException}} object passed to {{SensorErrorEventInit}}.
1245+
The <dfn attribute for="SensorErrorEvent">error</dfn> attribute must return the
1246+
value it was initialized to. It represents the {{DOMException}} object passed
1247+
to {{SensorErrorEventInit}}.
12481248

12491249
<h2 id="abstract-operations">Abstract Operations</h2>
12501250

0 commit comments

Comments
 (0)