Skip to content

Commit 3fb9b47

Browse files
committed
Applied @dlongley's suggestion on noting that local contexts introduced when a type-scoped context is in effect remain in effect in descendant node objects.
1 parent 3340bc2 commit 3fb9b47

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

index.html

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3410,6 +3410,9 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
34103410
the type is used; the previous in-scope <a>contexts</a> are placed back into
34113411
effect when traversing into another <a>node object</a>.</p>
34123412

3413+
<p class="note">Any property-scoped or local contexts that were introduced in the <a>node object</a>
3414+
would still be in effect when traversing into another <a>node object</a>.</p>
3415+
34133416
<p>When expanding, each value of <code>@type</code> is considered
34143417
(ordering them lexicographically) where that value is also a <a>term</a> in
34153418
the <a>active context</a> having its own <a>scoped context</a>. If so, that

0 commit comments

Comments
 (0)