Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[css-gaps-1] Computed value of row-rule-width when row-rule-style is none or hidden #11493

Closed
kbabbitt opened this issue Jan 13, 2025 · 1 comment

Comments

@kbabbitt
Copy link
Collaborator

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?

@astearns astearns moved this to FTF agenda items in CSSWG January 2025 meeting Jan 22, 2025
@astearns astearns moved this from FTF agenda items to Friday afternoon in CSSWG January 2025 meeting Jan 28, 2025
@css-meeting-bot
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Friday afternoon
Development

No branches or pull requests

2 participants