- From: Alan Gresley <alan@css-class.com>
- Date: Sat, 27 Apr 2013 23:57:14 +1000
- To: Brad Kemper <brad.kemper@gmail.com>
- CC: Håkon Wium Lie <howcome@opera.com>, "L. David Baron" <dbaron@dbaron.org>, "www-style@w3.org" <www-style@w3.org>
On 26/04/2013 5:13 AM, Brad Kemper wrote: > > On Apr 25, 2013, at 11:37 AM, Håkon Wium Lie <howcome@opera.com> > wrote: > >> Also sprach Brad Kemper: >> >>> I mentioned it in another thread full of other points, but how >>> do you feel about making 'overflow-x' and 'overflow-y' be based >>> on writing mode, so that 'overflow-x' overflowed to the left for >>> vertical-rl writing? >> >> +1 >> >> This matches Opera's intent, if not implementation (as Presto >> doesn't support vertical writing). >> >>> If there are compatibility concerns, this behavior could be >>> switched on with a separate property, such as >>> 'overflow-behavior: logical | physical', or something like that. >> >> I'd like to avoid such switches as they create more >> interdependencies. It's better to have names/values where the >> meaning is self-evident. For example, 'text-indent' depends on the >> writing direction, while 'margin-left' doesn't. > > So, do you think compatibility with existing overflow-x and > overflow-y using vertical writing mode in the wild is not a big > concern? Or do you think there should be two new, better-named > properties, such as 'overflow-inline' and 'overflow-block'? Brad. Can you give some examples? I have previously mentioned about a logical block progression [1 & 2] and where does visible overflow go. Håkon. This is a major issue with non page documents (or paging effects) in CJK. There would be plenty of hacks to render ths test case [3] in a logical manner where you arrived at the beginning (01) of the document and not it's end (30). Alan 1. http://lists.w3.org/Archives/Public/www-style/2012Jun/0540.html 2. http://lists.w3.org/Archives/Public/www-style/2010Oct/0645.html 3. http://css-class.com/test/css/bidi/kanji-test2.htm -- Alan Gresley http://css-3d.org/ http://css-class.com/
Received on Saturday, 27 April 2013 13:57:42 UTC