From 08cc1606e2b3f49e39fc05c8420937fde1ab5c09 Mon Sep 17 00:00:00 2001
From: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Date: Fri, 3 May 2019 18:47:33 +0200
Subject: [PATCH] Do not assign a default value to
 WakeLockRequestOptions.signal

In Web IDL, the following `WakeLockRequestOptions` instances in JavaScript
should have the same effect (a dictionary that does _not_ have the `signal`
member present):

    {}
    {signal: undefined}

which are different from

    {signal: null}

which means a `WakeLockRequestOptions` dictionary with one member, `signal`,
whose value is `null`.

Setting a default value to the nullable member `signal` means we'd always
have a `signal` member in the dictionary even when we do not set it at
all (first 2 cases), which is not needed and does not make sense.
---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 5db0327..3d44f5e 100644
--- a/index.html
+++ b/index.html
@@ -547,7 +547,7 @@ <h3>
       <section data-dfn-for="WakeLockRequestOptions"> <h3>The <dfn>WakeLockRequestOptions</dfn> dictionary</h3>
         <pre class="idl">
           dictionary WakeLockRequestOptions {
-            AbortSignal? signal = null;
+            AbortSignal? signal;
           };
         </pre>
         <p>