5 ms·

There's a brief mention in passing, but the lack of good support for CSS columns is really frustrating. I have a requirement on a project that I'm working on fo

There's a brief mention in passing, but the lack of good support for CSS columns is really frustrating. I have a requirement on a project that I'm working on for columns, but they just cannot be satisfactorily implemented in CSS alone, in any browser. Apart to resort to JavaScript instead.

scotth 13y ago
What's the issue?
- oneeyedpigeon 13y ago
  SO much. Mainly a) lack of support for control over element breaking (I haven't gone really in-depth with the spec, but even the most obvious things are supported terribly) b) the weird behaviour of margin collapsing (and adding extra margins - WTF?!)
  - strictfp 13y ago
    Just use tables. I know that everyone recommends against it, but IMO they are the only solution which works as expected. Everyone says they have a fancy workaround, but none of them works well enough. And besides, whats wrong with tables? Semantic HTML is hip again :-)
    - rimantas 13y ago
      Please, show, how do you make tables that work like CSS columns, i.e. reflow the content to fill the specified number of columns. Unless you hardcode content for each TD, but what the point then? And that's exactly what's wrong with tables (semantic purity aside)—they shackle you content to one specific structure, meanwhile using CSS for layout you can move your blocks around more or less freely.
      - oneeyedpigeon 13y ago
        Exactly. Instead of just resorting to tables, I'd be much more likely to resort to a couple of DIVs which would involve less markup and be less semantically incorrect. But the whole point is that I don't want to have to decide, on an article-by-article basis, exactly where my break between two columns should actually be.
- Achshar 13y ago
  For me atleast it was that they don't work when the page is printed in webkit/blink. That and browser support.
e12e 13y ago
I think the css-columns thing is flawed anyway. I'd much rather see: http://dev.w3.org/csswg/css-regions/ http://dev.w3.org/csswg/css-regions/ It's the only thing that makes sense if we want to allow that type of design on the web. It appears: http://adobe-webplatform.github.io/css-regions-polyfill/ http://adobe-webplatform.github.io/css-regions-polyfill/ works fine in eg. Firefox - but their example page degrades horribly with javascript disabled -- but that shouldn't be insurmountable -- the easiest might be to simply patch the layout with an onLoad or something (have the static site show something similar either without columns, or using css-columns or something...). edit: formatting

scotth 13y ago

What's the issue?

oneeyedpigeon 13y ago
SO much. Mainly a) lack of support for control over element breaking (I haven't gone really in-depth with the spec, but even the most obvious things are supported terribly) b) the weird behaviour of margin collapsing (and adding extra margins - WTF?!)
- strictfp 13y ago
  Just use tables. I know that everyone recommends against it, but IMO they are the only solution which works as expected. Everyone says they have a fancy workaround, but none of them works well enough. And besides, whats wrong with tables? Semantic HTML is hip again :-)
  - rimantas 13y ago
    Please, show, how do you make tables that work like CSS columns, i.e. reflow the content to fill the specified number of columns. Unless you hardcode content for each TD, but what the point then? And that's exactly what's wrong with tables (semantic purity aside)—they shackle you content to one specific structure, meanwhile using CSS for layout you can move your blocks around more or less freely.
    - oneeyedpigeon 13y ago
      Exactly. Instead of just resorting to tables, I'd be much more likely to resort to a couple of DIVs which would involve less markup and be less semantically incorrect. But the whole point is that I don't want to have to decide, on an article-by-article basis, exactly where my break between two columns should actually be.
Achshar 13y ago
For me atleast it was that they don't work when the page is printed in webkit/blink. That and browser support.

e12e 13y ago

I think the css-columns thing is flawed anyway. I'd much rather see: http://dev.w3.org/csswg/css-regions/ http://dev.w3.org/csswg/css-regions/ It's the only thing that makes sense if we want to allow that type of design on the web. It appears: http://adobe-webplatform.github.io/css-regions-polyfill/ http://adobe-webplatform.github.io/css-regions-polyfill/ works fine in eg. Firefox - but their example page degrades horribly with javascript disabled -- but that shouldn't be insurmountable -- the easiest might be to simply patch the layout with an onLoad or something (have the static site show something similar either without columns, or using css-columns or something...). edit: formatting