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: MURATA Makoto (FAMILY Given) <eb2m-mrt@asahi-net.or.jp>
Date: Tue, 08 Jun 2010 18:00:46 +0900
To: <www-style@w3.org>
Message-Id: <20100608180046.9634.B794FC04@asahi-net.or.jp>
> 
> Let's try to get an overview of the various proposals. In no
> particular order, I see:

I like your summary.  I reluctantly give up 1) and 2).  I buy 3) and 4).  In 
an ideal world, everything should have been logical, or every implementation 
and every page should be instantly changed.  But this is not so in this real world.
I have minor comments on 3) and 4), but won't mention them in this mail.

On top of 3) or 4), I am wondering if we can add some syntax 
sugar.   Such syntax sugar can be easily implemented by a preprocessor, 
and provides most of the advantages of logical properties or values.

For example:

p {margin-before:1cm; margin-after:2cm; margin-start:3cm; margin-end:4cm;
margin-logical-width:5cm;margin-logical-height:6cm;}

is equivalent to two rules:

p::ltr {margin-top:1cm;margin-bottom:2cm;margin-left:3cm; margin-right:4cm;
margin-width:5cm;margin-height:6cm;}

and 

p::ttb {margin-right:1cm; margin-left:2cm; margin-top:3cm; margin-bottom:4cm; 
margin-height:5cm; margin-width:6cm;}

This approach would work even for inline style attributes.  Comments?
 
Regards,

MURATA Makoto (FAMILY Given)
Received on Tuesday, 8 June 2010 09:01:21 GMT

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