diff --git a/index.html b/index.html
index 6c6aa58e..3ee79131 100644
--- a/index.html
+++ b/index.html
@@ -6572,7 +6572,7 @@ <h3>LoadDocumentCallback</h3>
       <pre class="idl">
         callback LoadDocumentCallback = Promise&lt;RemoteDocument> (
           USVString url,
-          optional LoadDocumentOptions? options
+          optional LoadDocumentOptions options = {}
         );
       </pre>
 
diff --git a/tests/expand-manifest.html b/tests/expand-manifest.html
index 145e21c4..398410d4 100644
--- a/tests/expand-manifest.html
+++ b/tests/expand-manifest.html
@@ -3217,6 +3217,34 @@ <h2>
             </dd>
           </dl>
         </dd>
+        <dt id='t0132'>
+          Test t0132 @base does not expand property keys
+        </dt>
+        <dd>
+          <dl class='entry'>
+            <dt>id</dt>
+            <dd>#t0132</dd>
+            <dt>Type</dt>
+            <dd>jld:PositiveEvaluationTest, jld:ExpandTest</dd>
+            <dt>Purpose</dt>
+            <dd>Property keys are expanded vocabulary-relative (`@vocab`, term definitions, compact IRIs with a defined prefix). `@base` is for document-relative IRI resolution where the algorithms pass that flag (e.g., certain `@id` and `@type` values), not for unmapped simple keys. With only `@base` set, an unmapped key like `name` has no vocabulary mapping and must be dropped; a relative `@type` token still resolves against the base. See IRI Expansion in the JSON-LD 1.1 Processing Algorithms and API.</dd>
+            <dt>input</dt>
+            <dd>
+              <a href='expand/0132-in.jsonld'>expand/0132-in.jsonld</a>
+            </dd>
+            <dt>expect</dt>
+            <dd>
+              <a href='expand/0132-out.jsonld'>expand/0132-out.jsonld</a>
+            </dd>
+            <dt>Options</dt>
+            <dd>
+              <dl class='options'>
+                <dt>specVersion</dt>
+                <dd>json-ld-1.1</dd>
+              </dl>
+            </dd>
+          </dl>
+        </dd>
         <dt id='tc001'>
           Test tc001 adding new term
         </dt>
diff --git a/tests/expand-manifest.jsonld b/tests/expand-manifest.jsonld
index 1fbd5efa..d6eaac5e 100644
--- a/tests/expand-manifest.jsonld
+++ b/tests/expand-manifest.jsonld
@@ -987,6 +987,14 @@
       "input": "expand/0131-in.jsonld",
       "expect": "expand/0131-out.jsonld",
       "option": {"specVersion": "json-ld-1.1"}
+    }, {
+      "@id": "#t0132",
+      "@type": [ "jld:PositiveEvaluationTest", "jld:ExpandTest" ],
+      "name": "@base does not expand property keys",
+      "purpose": "Property keys are expanded vocabulary-relative (`@vocab`, term definitions, compact IRIs with a defined prefix). `@base` is for document-relative IRI resolution where the algorithms pass that flag (e.g., certain `@id` and `@type` values), not for unmapped simple keys. With only `@base` set, an unmapped key like `name` has no vocabulary mapping and must be dropped; a relative `@type` token still resolves against the base. See IRI Expansion in the JSON-LD 1.1 Processing Algorithms and API.",
+      "input": "expand/0132-in.jsonld",
+      "expect": "expand/0132-out.jsonld",
+      "option": {"specVersion": "json-ld-1.1"}
     }, {
       "@id": "#tc001",
       "@type": ["jld:PositiveEvaluationTest", "jld:ExpandTest"],
diff --git a/tests/expand/0132-in.jsonld b/tests/expand/0132-in.jsonld
new file mode 100644
index 00000000..fd89fc38
--- /dev/null
+++ b/tests/expand/0132-in.jsonld
@@ -0,0 +1,9 @@
+{
+  "@context": {
+    "@version": 1.1,
+    "@base": "https://example.org/vocab/base/"
+  },
+  "@id": "https://example.org/doc",
+  "@type": "Thing",
+  "name": "value"
+}
diff --git a/tests/expand/0132-out.jsonld b/tests/expand/0132-out.jsonld
new file mode 100644
index 00000000..cee27d85
--- /dev/null
+++ b/tests/expand/0132-out.jsonld
@@ -0,0 +1,4 @@
+[{
+  "@id": "https://example.org/doc",
+  "@type": ["https://example.org/vocab/base/Thing"]
+}]