To follow up: would there then be a `translateLogical` or `rotateBlockInline` for 2D transforms that usually follow XY? What about 3D contexts? And `matrix`? I think most authors wouldn't mind using the "longhand" by defining each transform logically if it helps keep the code easy to understand, but some might like the convenience they find in `translate(Xem, Yem)` to be easy to reach for with logical transforms. Or flip it on its head and use a `transform-logical` property, and the "shorthands" (anything that doesn't have `X` or `Y`) as values. But I don't think people would like to have to use another property. -- GitHub Notification of comment by chriskirknielsen Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1544#issuecomment-694643173 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Friday, 18 September 2020 04:28:53 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:16 UTC