50

I have been trying CSS columns, but I can't get breaks to work. Here's the CSS so far:

#container { 
    width: 500px;
    column-count: 3;
    -moz-column-count: 3;
    -webkit-column-count: 3;
} 
h1 {
    break-after: always;
    -moz-column-break-after: always;
    -webkit-column-break-after: always;
}

And here's the relevant HTML:

<div id="container">
    <h1>The header of the first column</h1>
    <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit.</p>
    <p>Maecenas interdum mattis leo, id vehicula sapien ultricies et.</p>
    <p>Donec orci nunc, rhoncus ut convallis a, pretium quis elit.</p>
    <p>Aenean vulputate vulputate bibendum.</p>
    <p>Fusce imperdiet velit quis diam fermentum ut volutpat ipsum convallis.</p>
</div>

No matter if I do break-after: avoid, break-after: always, break-before: avoid or break-before: always I still get the same result. Nothing changes. Can somebody help me out? I have tested it in Firefox 4.6 and Safari 5.0.5.

Thanks

8
  • 3
    can you show us a screen shot of the desired result?
    – Alex
    Commented Jun 21, 2011 at 10:56
  • desired result is achieved in Chrome, i.e. first <p> starts in the new column. not sure why Safari ignores it as it's all inline with their spec: developer.apple.com/library/safari/#documentation/…
    – Ruslan
    Commented Jun 21, 2011 at 11:04
  • works fine in FF4 too...
    – Alex
    Commented Jun 21, 2011 at 11:07
  • ? not for me it doesn't.
    – Ruslan
    Commented Jun 21, 2011 at 11:14
  • +1 from me for pointing out non-working CSS property. I'll keep this in mind.
    – Ruslan
    Commented Jun 21, 2011 at 11:23

7 Answers 7

95

The CSS column break rules are poorly supported, but I've found a workaround that does something close enough. Instead of writing this:

 <div class="columns">
    <h1>Heading</h1>
    <p>Paragraph</p>
 </div>

I'm writing this:

 <div class="columns">
    <div class="keeptogether">
       <h1>Heading</h1>
       <p>Paragraph</p>
    </div>
 </div>

Then the CSS looks like this:

 div.columns {
    column-width: 300px;
    -moz-column-width: 300px;
    -webkit-column-width: 300px;
 }
 div.keeptogether {
    display: inline-block;
    width: 100%;
 }

You can see the results here, for example.

0
9

I encountered the same kind of issue and solved it as follows.

My main issue was not inserting a break after each "heading/paragraph" block but avoiding a column break inside a "heading/paragraph" block.

The solution is easy :

  1. Enclose each "heading/paragraph" block in a span tag.

  2. In the CSS, add a reference to the span tag, with the following code in it :

    display: inline-block; width: 100%;

The little drawback is that this may leave blank areas at the bottom of some columns.

In my case the whole css is as follows (div defines the global formatting of the data flow):

div {
    -webkit-column-width: 20em; /* 20em wide */
    -webkit-column-gap: 2em;  /* 2em gap */
    -webkit-column-rule: 1px solid #eee;   /* 1px border between columns */
    -webkit-column-count: 3; /* 3 columns max! */

    -moz-column-width: 20em;
    -moz-column-gap: 2em;
    -moz-column-rule: 1px solid #eee; 
    -moz-column-count: 4;

    -ms-column-width: 20em;
    -ms-column-gap: 2em;
    -ms-column-rule: 1px solid #eee; 
    -ms-column-count: 3;

    column-width: 20em;
    column-gap: 2em;
    column-rule: 1px solid #eee; 
    column-count: 3;

    padding: 5px;
}

.tokeeptogether {
    display: inline-block;
    width: 100%;
}
1
  • That is exactly what I've done for my application. +1
    – kyb
    Commented Feb 13, 2022 at 19:54
5

Here's what the problem is - no column break after "The header" in Safari and Firefox: enter image description here

According to this, this and this the column breaks don't work as yet.

2

Column breaks have never been supported in previous versions of Safari - my guess this is still the case. It is rather weird that Apple have written that it is supported since 3.0 though (Safari documentation about column breaks) ...

Same goes with Firefox. Chrome is the only browser which supportes almost all, if not all, column controls.

0

It seems the h1 in the sample is exactly big enough to always cause a break after it, if you shorten it to just "The head", the break-after has an effect.

2
  • Sorry, that's not true. See my screenshot.
    – Ruslan
    Commented Jun 21, 2011 at 11:21
  • Oh, I forgot to re-test in Firefox. But it's true for Chrome. Commented Jun 21, 2011 at 11:26
0

If I'm not mistaken, you want the header to go across all columns and let only the following siblings to be split, right?
I'm afraid column breaks still do not work as intended, so - it may not be the most "orthodox" solution, but saved me - I fixed this with some funky styling:

Essential HTML:

<div class="container">
  <h1>Header</h1>
  <p>First paragraph</p>
  <p>Second paragraph</p>
  <p>Third paragraph</p>
</div>

Essential CSS:

.container{
  column-count:3; /* Add necessary prefixes */
  padding-top:2em;
  position:relative;
}
.h1{
  position:absolute;
  top:0;
}

Absolute positioning exempts that element from the columns flow and seems to work just fine.

P.S.: just noticed the post is rather old...well, I hope this helps someone else, support for these CSS properties hasn't improved that much

0
break-after: 

is incorrect, should be:

column-break-after

also, no one has mentioned these properties:

-webkit-column-span: all;
-moz-column-span: all;
column-span: all;

which sound like they could be useful here

edit: also, it should be mentioned that support for columns is now pretty decent actually, albeit with the use of vendor prefixes.

column-fill

is still not supported by most browsers but AFAIK the majority of other properties are

4
  • 1
    There's no column-break-after. break-after is correct. Commented Nov 10, 2016 at 16:33
  • any reliable source where it is stated Commented May 13, 2018 at 9:00
  • 1
    You should check the date before leaving comments! At the time of writing, it was correct: w3.org/TR/2005/WD-css3-multicol-20051215/#column-break-after1 I can see that the spec has now changed...
    – mr_reamer
    Commented May 14, 2018 at 11:18
  • 1
    @mr_reamer if the spec has changed, shouldn't you update your post to reflect this?
    – clayRay
    Commented Feb 3, 2020 at 2:54

Not the answer you're looking for? Browse other questions tagged or ask your own question.