Replies: 1 comment
-
|
Thank you for suggesting this. There have discussions about this for a couple of months in another feature request that was only for margin-inline, I hope your separate request gets more eyes on this issue. See also the comment from @OverflowCat with insightful information on top to bottom writing direction usage in Asia: #1483 (reply in thread) Clearly more and more websites are using logical properties, including the block axis, I don't see why Tailwind should not support the last remaining logical properties instead of only supporting a couple of them, it makes it very confusing and annoying to me. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Tailwind supports only a subset of logical properties - utilities based on inline-axis:
margin-inline-start→ → →ms-*margin-inline-end→ → → →me-*padding-inline-start→ → →ps-*padding-inline-end→ → → →pe-*border-inline-start-width→border-s-*border-inline-end-width→ →border-e-*inset-inline-start→ → → →start-*inset-inline-end→ → → → →end-*However, it does NOT support any block-axis properties:
margin-block-startmargin-block-endpadding-block-startpadding-block-endborder-inline-start-widthborder-inline-end-widthinset-block-startinset-block-endPrevious issues to improve logical properties mainly focus on improving LTR/RTL support, but it's only a subset of logical properties. Tailwind is missing a significant portion of the logical spec.
Beta Was this translation helpful? Give feedback.
All reactions