You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per CSS Multicol 1, if column-rule-style is none or hidden, then the computed value of column-rule-width will be 0.
Gaps 1 contains text to preserve this behavior for backwards compatibility. Gaps 1 also introduces corresponding new properties in the row direction. Should this relationship between column-rule-style and column-rule-width be carried over into the row properties?
The text was updated successfully, but these errors were encountered:
The CSS Working Group just discussed [css-gaps-1] Computed value of row-rule-width when row-rule-style is none or hidden, and agreed to the following:
RESOLVED: don't apply the hidden/none quirk to row-rule, for reasons in #11494
The full IRC log of that discussion
<TabAtkins> kbabbitt: similar question to previous
<TabAtkins> kbabbitt: do we want to carry the back-compat beahvior over to the new row-rule-* properties
<TabAtkins> kbabbitt: guessing the answer is no
<TabAtkins> kbabbitt: seems we're leaning toward preserving the author-exposed value, with minimal back-compat
<TabAtkins> kbabbitt: so we don't apply to the row props
<TabAtkins> astearns: so proposed is "don't apply the hidden/none quirk to row-rule, for reasons in 11494"
<TabAtkins> RESOLVED: don't apply the hidden/none quirk to row-rule, for reasons in #11494
Per CSS Multicol 1, if
column-rule-style
isnone
orhidden
, then the computed value ofcolumn-rule-width
will be 0.Gaps 1 contains text to preserve this behavior for backwards compatibility. Gaps 1 also introduces corresponding new properties in the row direction. Should this relationship between column-rule-style and column-rule-width be carried over into the row properties?
The text was updated successfully, but these errors were encountered: