- From: Nicolas Hoffmann via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Aug 2022 13:00:43 +0000
- To: public-css-archive@w3.org
Yes, there are some cases where we would really need this, I'm facing one right now for a custom toggle (using transforms for smooth animations): LTR: ![image](https://user-images.githubusercontent.com/2578321/187206369-1e6bf29b-e4a4-4ffd-8b21-ef6708ad9baa.png) I'm doing: ``` transform: translateX(<value>); ``` for active state. But it will give this in RTL: ![image](https://user-images.githubusercontent.com/2578321/187206475-d655662e-3c58-45b1-a7d7-d2a729134471.png) I have to do: ``` transform: translateX(-<value>); ``` To get the proper display: ![image](https://user-images.githubusercontent.com/2578321/187206433-96f9ce50-2811-4cef-9bff-74a2d4ecef59.png) Something like: `translate-inline-start` would replace something like: ``` [dir="rtl] .selector { transform: translateX(-<value>); } ``` And same for `translateY`, we would go for translate-block-start. For `translateZ`, I guess i18n does not encounter negative 3D written stuff... so it's okay :D Migrated from https://github.com/w3c/csswg-drafts/issues/1788 -- GitHub Notification of comment by nico3333fr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1544#issuecomment-1230254694 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 August 2022 13:00:45 UTC