Skip to content

Commit

Permalink
Address comments from blu25
Browse files Browse the repository at this point in the history
  • Loading branch information
VergeA committed Nov 13, 2024
1 parent 9259406 commit 8bce1ec
Showing 1 changed file with 62 additions and 52 deletions.
114 changes: 62 additions & 52 deletions spec.bs
Original file line number Diff line number Diff line change
Expand Up @@ -3317,58 +3317,68 @@ left over to be leaked to the next {{Document}}.
Fenced frames use an additional reserved navigation target "<code>_unfencedTop</code>" to navigate.
This section patches the relevant portions of the [[HTML]] spec to add <code>_unfencedTop</code>.

Extend [=valid navigable target name or keyword=] to include a new keyword named <code>_unfencedTop
</code>.

In the following paragraph, change "top" to refer to the [=navigable/traversable navigable=] of the
[=navigable=] that the link or script is in. Add an additional clause to the same sentence that
reads: "outermost top" is the [=top-level traversable=] of the [=navigable=] that the link or
script is in.

Note: This change is necessary because this spec adds a distinction between [=navigable/traversable
navigable=] and [=top-level traversable=], which were previously functionally equivalent.

In the table below, add a column named "Effect in a fenced frame". The value for all rows in
this column is the same as "ordinary effect". Then, add two rows which read:

<table>
<thead>
<tr>
<th rowspan=2>Keyword</th>
<th rowspan=2>Ordinary effect</th>
<th colspan=2>Effect in an <code>iframe</code> with...</th>
<th rowspan=2>Effect in a fenced frame</th>
</tr>
<tr>
<th><code data-x="">sandbox=""</code></th>
<th><code data-x="">sandbox="allow-top-navigation"</code></th>
</tr>
</thead>

<tbody>
<tr>
<td><code>_unfencedTop</code> if outermost top is current</td>
<td>current</td>
<td>current</td>
<td>current</td>
<td>current</td>
</tr>
<tr>
<td><code>_unfencedTop</code> if outermost top is not current</td>
<td>outermost top</td>
<td>none</td>
<td>outermost top</td>
<td>outermost top</td>
</tr>
</tbody>
</table>

Add an extra step to [=the rules for choosing a navigable=] between the current steps 6 and 7, that
reads:

6.5. Otherwise, if name is an ASCII case-insensitive match for "_unfencedTop" and
|currentNavigable|'s [=navigable/traversable navigable=] is a [=fenced navigable container/fenced
navigable=], set <var ignore=''>chosen</var> to |currentNavigable|'s [=top-level traversable=].
<div algorithm="unfenced-top-keyword">
Modify [=valid navigable target name or keyword=] to include a new keyword named <code>
_unfencedTop</code>.

Modify the below paragraph to replace the following text:

* "top" means the [=top-level traversable=] of the [=navigable=] that the link or script is in,

with:

* "top" means the [=navigable/traversable navigable=] of the [=navigable=] that the link or
script is in, "outermost top" means the [=top-level traversable=] of the [=navigable=] that
the link or script is in,

Note: This change is necessary because this spec adds a distinction between
[=navigable/traversable navigable=] and [=top-level traversable=], which were previously
functionally equivalent.

In the table below, add a column named "Effect in a fenced frame". The value for all existing
rows in this column is the same as "ordinary effect". Then, add two rows which read:

<table>
<thead>
<tr>
<th rowspan=2>Keyword</th>
<th rowspan=2>Ordinary effect</th>
<th colspan=2>Effect in an <code>iframe</code> with...</th>
<th rowspan=2>Effect in a fenced frame</th>
</tr>
<tr>
<th><code data-x="">sandbox=""</code></th>
<th><code data-x="">sandbox="allow-top-navigation"</code></th>
</tr>
</thead>

<tbody>
<tr>
<td><code>_unfencedTop</code> if outermost top is current</td>
<td>current</td>
<td>current</td>
<td>current</td>
<td>current</td>
</tr>
<tr>
<td><code>_unfencedTop</code> if outermost top is not current</td>
<td>outermost top</td>
<td>none</td>
<td>outermost top</td>
<td>outermost top</td>
</tr>
</tbody>
</table>
</div>

<div algorithm="unfenced-top-rules">
Add an extra step to [=the rules for choosing a navigable=] between the current steps 6 and 7,
that reads:

6.5. Otherwise, if name is an ASCII case-insensitive match for "_unfencedTop" and
|currentNavigable|'s [=navigable/traversable navigable=] is a [=fenced navigable container/fenced
navigable=], set <var ignore=''>chosen</var> to |currentNavigable|'s [=top-level traversable=].
</div>

<h3 id=page-visibility>Page visibility</h3>

Expand Down

0 comments on commit 8bce1ec

Please sign in to comment.