diff --git a/specs/latest/1.0/index.html b/specs/latest/1.0/index.html
index 40ad9e3489..356c7ffd8e 100644
--- a/specs/latest/1.0/index.html
+++ b/specs/latest/1.0/index.html
@@ -3195,7 +3195,8 @@
WebGL rendering context. Events are sent using the DOM Event System [DOM3EVENTS],
and are dispatched to the HTMLCanvasElement associated with the WebGL rendering context.
The types of status changes that can trigger a WebGLContextEvent event are
- the loss of the context, the restoration of the context, and
+ the loss of the context, the restoration of the context,
+ a significant change in the system GPU's capabilities, and
the inability to create a context.
@@ -3379,6 +3380,42 @@
initializeGame();
+
+
+
+ When the user agent detects that the capabilities of the
+ WebGLRenderingContext context have been significantly changed
+ by the system, such as parameters indicating the maximum values the
+ context supports, it must run the following steps:
+
+
+
+ - Let canvas be the context's
+ canvas.
+
+ - Queue a task to
+ perform the following step:
+
+
+
+ - Fire a WebGL context event named
+ "webglcontextchanged" at canvas, with its
statusMessage attribute set
+ to "".
+
+
+
+
+
+
+
+
+ This event is designed to be mostly informative, and usually only applicable to content
+ that has tested and exceeded the minimum requirements for some context limits. In this
+ case, on a system with multiple GPUs, if the underlying GPU that a context is using
+ is changed by the system to one that is less capable, the content may need to
+ reset itself for the new limits. The majority of content will not need to handle this event.
+
+