Skip to content

Commit 76245cd

Browse files
committed
[css-flexbox] Tweak wording of note about spatial navigation. Fixes #1677.
1 parent f6973a2 commit 76245cd

File tree

1 file changed

+22
-4
lines changed

1 file changed

+22
-4
lines changed

css-flexbox/Overview.bs

Lines changed: 22 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1372,10 +1372,10 @@ Reordering and Accessibility</h4>
13721372
This section does not preclude respecting the 'order' property
13731373
when determining element ordering in such spatial navigation modes;
13741374
indeed it would need to be considered for such a feature to work.
1375-
However a UA that uses 'order' in determining sequential navigation,
1376-
but does not otherwise account for spatial relationships among elements
1377-
(as expressed by the various layout features of CSS including and not limited to flex layout),
1378-
is non-conforming.
1375+
But 'order' is not the only (or even the primary) CSS property
1376+
that would need to be considered for such a spatial navigation feature.
1377+
A well-implemented spatial navigation feature would need to consider
1378+
all the layout features of CSS that modify spatial relationships.
13791379

13801380
<!--
13811381
████████ ██ ████████ ██ ██ ██ ████ ██ ██ ████████ ██████
@@ -3475,6 +3475,24 @@ Clarifications</h4>
34753475
<li>Made sure that <a>main size</a> and <a>cross size</a> are defined
34763476
for <a>flex containers</a> as well as for <a>flex items</a>.
34773477
(<a href="https://github.com/w3c/csswg-drafts/issues/981">Issue 981</a>)
3478+
<li>Tweaked final clarifying sentence of note about spatial navigation.
3479+
(<a href="https://github.com/w3c/csswg-drafts/issues/1677">Issue 1677</a>)
3480+
<blockquote>
3481+
<p class="note">
3482+
User agents, including browsers, accessible technology, and extensions,
3483+
may offer spatial navigation features.
3484+
This section does not preclude respecting the 'order' property
3485+
when determining element ordering in such spatial navigation modes;
3486+
indeed it would need to be considered for such a feature to work.
3487+
<del>However a UA that uses 'order' in determining sequential navigation,
3488+
but does not otherwise account for spatial relationships among elements
3489+
(as expressed by the various layout features of CSS including and not limited to flex layout),
3490+
is non-conforming.</del>
3491+
<ins>But 'order' is not the only (or even the primary) CSS property
3492+
that would need to be considered for such a spatial navigation feature.
3493+
A well-implemented spatial navigation feature would need to consider
3494+
all the layout features of CSS that modify spatial relationships.</ins>
3495+
</blockquote>
34783496
</ul>
34793497

34803498
<h3 id="changes-20160301">

0 commit comments

Comments
 (0)