Authors who work exclusively in top-to-bottom, left-to-right languages tend to map top and bottom onto the block axis and left and right onto the inline axis without much thought. Logical properties formalize that mapping: height becomes block-size, border-right becomes border-inline-end, padding: 0 1em becomes padding-inline: 1em, and margin-top becomes margin-block-start.
Where support gets uneven
The single-axis longhands are broadly reliable, but the flow-relative shorthands are a different story. Setting a start and end value in one declaration — the logical equivalent of margin: 1rem 0 — via margin-block fails in some browsers. The lag makes sense: unlike margin-block-end, a shorthand like margin-block has no direct mapping onto a pre-logical CSS property, so there is nothing for older engines to fall back on. Caveats of this kind are enough to make a wary developer hold back from adopting the syntax everywhere.
Why the block/inline model is still worth adopting
For sites that are still English-only, consistency pays off later. Writing layouts with logical properties throughout makes a translation into a right-to-left or vertical writing mode far less painful, and the block/inline mental model is arguably clearer to reason about on its own terms than physical directions are.
The cost of assuming one writing mode
Adam Argyle and Oriol Brufau make the case sharply: non-logical properties only fit a single "language style." Their illustration is worth quoting directly.
In English, letters and words flow left to right while paragraphs are stacked top to bottom. In traditional Chinese, letters and words are top to bottom while paragraphs are stacked right to left. In just these 2 cases, if we write CSS that puts "margin top" on a paragraph, we're only appropriately spacing 1 language style. If the page is translated into traditional Chinese from English, the margin may well not make sense in the new vertical writing mode.



