W3C home > Mailing lists > Public > www-style@w3.org > June 2010

Re: [css3-text-layout] New editor's draft - margin-before/after/start/end etc.

From: Brad Kemper <brad.kemper@gmail.com>
Date: Tue, 8 Jun 2010 09:52:23 -0700
Cc: John Daggett <jdaggett@mozilla.com>, MURAKAMI Shinyu <murakami@antenna.co.jp>, "Tab Atkins Jr." <jackalmage@gmail.com>, Boris Zbarsky <bzbarsky@mit.edu>, www-style list <www-style@w3.org>
Message-Id: <BE0F2552-BC24-4D10-A46E-9754BA2A6D9F@gmail.com>
To: Håkon Wium Lie <howcome@opera.com>

On Jun 8, 2010, at 12:26 AM, Håkon Wium Lie wrote:

> Also sprach John Daggett:
> 
>>> I think the cost for implementations will not be big problem in such
>>> future.
>> 
>> I think you're underestimating the impact of this change.  You are basically
>> virtualizing top/bottom/left/right, so any other property that uses 
>> top/bottom/left/right needs an expanded set of values or requires redefinition.
>> 
>> Other properties in CSS 2.1:
>> 
>> 'background-position'
>> 'caption-side'
>> 'clear'
>> 'float'
>> 'text-align'
>> 'vertical-align'
> 
> And, even:
> 
>  'top'
>  'right'
>  'bottom'
>  'left'

and...

'width'
'height'
'overflow-x'
'overflow-y'


> 
>> CSS3 Paged Media (?)
> 
> I would think so. Today we, e.g., have:
> 
>  @page :left  { @bottom-left-corner { ... }}
>  @page :right { @bottom-right-corner { ... }}
>  @page :first { @bottom-left-corner { ... }}
> 
> Lots of left and rights and tops and bottoms there.
> 
>> CSS3 Transitions (logical properties can be transitioned?)
> 
> ERROR: My head ran out of memory trying to compute the consequences :)
> 
> Cheers,
> 
> -h&kon
>              Håkon Wium Lie                          CTO °þe®ª
> howcome@opera.com                  http://people.opera.com/howcome
> 
Received on Tuesday, 8 June 2010 17:01:14 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:28 GMT