Add a section describing how to lay out tables with braille CSS .
include drawing of box model
idea: make the ::table-by(x) rule more intuitive/expressive by (assuming render-table-by: a b c):
changing the meaning of table::table-by(a) to table and
changing the meaning of table::table-by(b)to what currently is meant by table::table-by(a).
What is currently meant by table::table-by(c) can in most cases (when it is actually useful) be achieved by expanding render-table-by to a b c d.
With this new definition table::table-by(a)::list-item would always correspond with one "a", regardless of the value of render-table-by. So you could e.g. have a rule table::table-by(rowgroup)::list-item { ... } which would be used to style a "rowgroup" when render-table-by: rowgroup row but would be ignored when render-table-by: row. A rule table::table-by(row)::list-item { ... } would be used to style a "row" in both cases.
Add a section describing how to lay out tables with braille CSS .
idea: make the
::table-by(x)
rule more intuitive/expressive by (assumingrender-table-by: a b c
):table::table-by(a)
totable
andtable::table-by(b)
to what currently is meant bytable::table-by(a)
.table::table-by(c)
can in most cases (when it is actually useful) be achieved by expandingrender-table-by
toa b c d
.With this new definition
table::table-by(a)::list-item
would always correspond with one "a", regardless of the value ofrender-table-by
. So you could e.g. have a ruletable::table-by(rowgroup)::list-item { ... }
which would be used to style a "rowgroup" whenrender-table-by: rowgroup row
but would be ignored whenrender-table-by: row
. A ruletable::table-by(row)::list-item { ... }
would be used to style a "row" in both cases.See: