Skip to content

Commit 5bb6fbc

Browse files
yiyixdandclark
authored andcommitted
Update note on OffscreenCanvas being an event target
Part of whatwg#7130.
1 parent 302559e commit 5bb6fbc

1 file changed

Lines changed: 7 additions & 3 deletions

File tree

‎source‎

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -66769,9 +66769,13 @@ interface <dfn interface>OffscreenCanvas</dfn> : <span>EventTarget</span> {
6676966769
attribute <span>EventHandler</span> <span data-x="handler-offscreencanvas-oncontextrestored">oncontextrestored</span>;
6677066770
};</code></pre>
6677166771

66772-
<p class="note"><code>OffscreenCanvas</code> is an <code>EventTarget</code> so that WebGL can
66773-
fire <code data-x="">webglcontextlost</code> and <code data-x="">webglcontextrestored</code>
66774-
events at it. <ref spec=WEBGL></p>
66772+
<p class="note"><code>OffscreenCanvas</code> is an <code>EventTarget</code>, so both
66773+
<code>OffscreenCanvasRenderingContext2D</code> and WebGL can fire events at it.
66774+
<code>OffscreenCanvasRenderingContext2D</code> can fire <code
66775+
data-x="event-contextlost">contextlost</code> and <code
66776+
data-x="event-contextrestored">contextrestored</code>, and WebGL can fire <code
66777+
data-x="">webglcontextlost</code> and <code data-x="">webglcontextrestored</code>. <ref
66778+
spec=WEBGL></p>
6677566779

6677666780
<p><code>OffscreenCanvas</code> objects are used to create rendering contexts, much like an
6677766781
<code>HTMLCanvasElement</code>, but with no connection to the DOM. This makes it possible to

0 commit comments

Comments
 (0)