- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Oct 2018 13:54:19 +0000
- To: public-fxtf-archive@w3.org
Thanks for filing this! Just adding some notes and thoughts: I extended your demo with an example of using the technique of adding a logical-flip matrix: tldr; `transform: --var(logical-flip) translate(inline, block) --var(logical-flip)` https://codepen.io/flackr/pen/zmMOPd?editors=1100 It's important to note that you have to undo this logical flip or else the content would be flipped as well. I wonder if instead of adding logical to each transform function we should add a logical "transform-function" which produces the correct flip for the writing mode. I suspect logical rotation does in fact make sense. If you consider cases such as an arrow that turns to point at some text, the rotation direction will depend on writing direction. For transform-origin, we'd need to add logical keywords to replace top/left/bottom/right, e.g. (block-)start/center/end and (inline-)start/center/end. For interpolation, I assume we want translate(x, y) to be interpolable with the logical equivalent which is perhaps an argument that the logical transforms should implicitly alias to the physical (or vice versa)? -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/311#issuecomment-432666355 using your GitHub account
Received on Wednesday, 24 October 2018 13:54:20 UTC