On 19/9/15 13:26, Koji Ishii wrote: > The original topic is just about serialization, used in > getComputedStyle() and a few other places. Jonathan might need to > resolve it now, and I need it too very soon. Can we simply straw poll on > the next conf call, resolve, and do other discussions after that? Yes, please -- I'm implementing this in gecko right now, so clarification on this would be really useful. > > <div id=a style="text-orientation:sideways"></div> > <div id=b style="text-orientation:sideways-right"></div> > <script> > console.log(getComputedStyle(a).style.textOrientation); > console.log(getComputedStyle(b).style.textOrientation); > </script> > > Option A: it prints "sideways" and "sideways-right" > Option B: it prints "sideways" and "sideways" > Option C: it prints "sideways-right" and "sideways-right" > > Current situation: > * Jonathan, Florian, and I prefer B. > * Takao prefers C. > * fantasai didn't show her preference IIUC but proposing a rename to > "sideways-lr". > >> I think I would like to investigate the backwards-compat impact >>of switching to 'text-orientation: sideways-rl' and dropping >>the other keywords, since that would be a little easier to type, >>but also clearer and more consistent with the corresponding >>writing-mode' keywords... what is your opinion on that, if it >>is feasible? > > I disagree. 'writing-mode' is about direction, so "l-to-r" and "r-to-l" > makes sense. 'text-orientation' is about orientation, so "right" makes > sense. And I agree with Koji here: I don't think 'sideways-rl' is good as a 'text-orientation' value. This property is distinct from 'writing-mode' and it's better not to confuse the values of the two. So my preference is still the simple 'sideways', with the alias 'sideways-right' supported for backward compatibility (option B above). JKReceived on Saturday, 19 September 2015 13:46:52 UTC
This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:53 UTC