css - What happened to `column-span: ` -



css - What happened to `column-span: <integer>` -

searching functionality, came across 2001 draft, specified column-span defined none | | <integer> | inherit. don’t none (spans no columns? mean display:none‽), other that, it’s nice. comes useful picture.

code sth. along lines of:

article { column-count: 3 } h1 { column-span: } h2 { column-span: 2 }

a bit history: abolished in 2005. 2007, re-introduced values 1 | all, wich became none | all 2011 (reintroducting nonsensical none).

my question: why property badly curtailed? there reasoning behind that? (and behind none)

in current draft @ least, property name column-span means “spans several columns” , value none means “no” or “false.” in december 2009 draft, things more natural, property interpreted “number of columns spanned” , initial value 1 , not none.

in general, identifiers in css misleading , may reflect various stages of planning—think white-space, affects line breaking in general, not text, or letter-spacing, affects characters, not letters.

based on have read in various discussions, reason limiting values 2 (no spanning, spanning all) implementing other values different , more complicated. moreover, demand such feature appears considerably more limited basic functionality.

this sounds realistic, since basic multi-column layout has poor support: don’t think major browser supports under proposed standard names (but back upwards under browser-specific property names), , there not seem back upwards column-span: all under name. (rumors safari supports it, tests on win 7 version don’t confirm this.)

css css3 columnspan

Comments

Popular posts from this blog

How do I check if an insert was successful with MySQLdb in Python? -

delphi - blogger via idHTTP : error 400 bad request -

postgresql - ERROR: operator is not unique: unknown + unknown -