W3C home > Mailing lists > Public > www-style@w3.org > January 2009

Re: [css3-page][css3-multicol] margins at page or column breaks

From: MURAKAMI Shinyu <murakami@antenna.co.jp>
Date: Sun, 11 Jan 2009 17:30:31 +0900
To: Hakon Wium Lie <howcome@opera.com>
Cc: www-style@w3.org
Message-Id: <20090111170828.A0BF.C598BCD7@antenna.co.jp>

MURAKAMI Shinyu <murakami@antenna.co.jp> wrote on 2009/01/10 2:17:38
> 
> Håkon Wium Lie <howcome@opera.com> wrote on 2009/01/09 23:09:50
> > 
> > Also sprach MURAKAMI Shinyu:
> > 
> >  > I think we need new properties such as the following:
> >  > 
> >  > Name: margin-before-conditionality, margin-after-conditionality
> >  > Value: discard-at-break | discard | retain
> >  > Initial: discard-at-break
> >  > Inherited: no
> >  > Applies to: block-level elements
> >  > 
> >  > The 'margin-before-conditionality' affects the leading margin
> >  > (margin-top if block-progression is top-to-bottom) and the 
> >  > 'margin-after-conditionality' affects the trailing margin 
> >  > (margin-bottom if block-progression is top-to-bottom).
> > 
> > This looks complex, and I don't really like inter-dependent properties. 
...
> I think still 'margin-before-conditionality: retain' (or something
> better) is needed here.


What if the margin-* properties themselves have optional keywords?
This will avoid inter-dependent problem.

Name: margin-top, margin-right, margin-bottom, margin-left
Value: <margin-width> [discard | retain]?


-- 
Shinyu Murakami
http://www.antennahouse.com
Antenna House Formatter
http://www.antenna.co.jp/AHF/en/
Received on Sunday, 11 January 2009 08:31:12 GMT

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