@@ -315,24 +315,31 @@ scrollable element.
315
315
316
316
: <code> auto</code>
317
317
:: If only one direction is scrollable, selects that direction.
318
- Otherwise selects the direction along the [=block axis=] .
318
+ Otherwise selects the direction along the [=block axis=] , conforming to
319
+ writing mode and directionality.
319
320
320
321
: <code> block</code>
321
- :: Selects the direction along the [=block axis=] .
322
+ :: Selects the direction along the [=block axis=] , conforming to writing mode
323
+ and directionality.
322
324
323
325
: <code> inline</code>
324
- :: Selects the direction along the [=inline axis=] .
326
+ :: Selects the direction along the [=inline axis=] , confirming to writing mode
327
+ and directionality.
325
328
326
329
: <code> horizontal</code>
327
- :: Selects the horizontal direction.
330
+ :: Selects the physical horizontal direction (ignoring writing mode and
331
+ directionality).
328
332
329
333
: <code> vertical</code>
330
- :: Selects the vertical direction.
334
+ :: Selects the physical vertical direction (ignoring writing mode and
335
+ directionality).
331
336
332
- <div class="issue">
337
+ Note: Having both logical (block/inline) and physical (vertical/horizontal)
338
+ directions allows web developers to animate both logical (e.g.
339
+ margin-inline-start) and physical (e.g. transform) properties with good
340
+ behavior under different directionalities and writing modes.
333
341
334
- Should the physical directions ("horizontal" and "vertical") be removed, leaving
335
- only the logical directions ("block" and "inline")?
342
+ <div class="issue">
336
343
337
344
What about a value that means, "the longest scroll direction"? That would be
338
345
more reliable than "auto" for the case where layout differences could mean that,
0 commit comments