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

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

From: Håkon Wium Lie <howcome@opera.com>
Date: Fri, 9 Jan 2009 15:09:50 +0100
Message-ID: <18791.23214.106923.493090@opera.com>
To: MURAKAMI Shinyu <murakami@antenna.co.jp>
Cc: www-style@w3.org

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. 

Instead, I suggest encouraging authors to use 'padding' when if the
don't want to see space discarded, and 'margin' otherwise.

 > >  > 3. Margins at beginning of multi-column content will be set to zero?
 > > 
 > > No.
 > ^^^^^

 > >  > 3. Margins at beginning of multi-column content will be set to zero?
 > >  > Firefox=Yes
 > >  > Safari=No
 > >  > Prince=Yes
 > >  > PDFreactor=? (multi-column not yet supported)
 > > 
 > > This should definitely be yes.
 >                             ^^^^
 > Correct?

As you can see, I'm torn :)

Following the principle above, I do think margins should be discarded
in case of doubt -- my vote is yes.

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Friday, 9 January 2009 14:10:33 GMT

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