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
{{ message }}
Repository navigation
[css-multicol] z-order of column rule and column scrolling #1739
There is a discussion in October 2013 suggesting a change to this wording, plus the addition of a clarification re: scrolling:
Column rules are painted just above the border of the multicol element. For scrollable multicol elements, note that while the border and background of the multicol element obviously aren't scrolled, the rules need to scroll along with the columns.
I don't see any resolution to this discussion, it doesn't seem to have been edited into the spec. Posting it here as an open issue.
This is one of a list of legacy issues I'm digging out of the www-style archives.
An example so we can see how this currently behaves, use Firefox to see the overflowing item painted over the rule (existing clipping interop issue means you can't see that in other browsers) https://bugs.chromium.org/p/chromium/issues/detail?id=269061#c19
The Working Group just discussed Multicolumn issues, and agreed to the following resolutions:
RESOLVED: Apply proposed edit from Oct 2013 to spec.
The full IRC log of that discussion
<Rossen> Topic: Multicolumn issues
<Rossen> github: https://github.com//issues/1739
<eae> rachelandrew: These first three issues are ones I dig out from the mailing list archive. They're all quite old.
<eae> rachelandrew: Things we've discussed, not sure what to do so brinng them up here.
<eae> rachelandrew: First one. z-order for column scrolling.
<eae> rachelandrew: Suggested change to wording.
<eae> rachelandrew: Is this something we want to add into the spec or do we need to dicuss it?
<eae> florian: Do we have interop on the proposed wording?
<eae> rachelandrew: There is an issue with overflow which as resolved a while ago, interop on the issue across browsers as far as I can tell.
<eae> rachelandrew: Firefox does not support spanning.
<eae> Rossen: Firefox is different due to that.
<eae> rachelandrew: Right, relating to the fact that thay haven't implemented it.
<eae> florian: The things that is linked to is not a minimized test case. Is an example.
<eae> rachelandrew: Correct.
<eae> Proposed resolution: Apply proposed edit from Oct 2013 to spec.
<bkardell_> sfbay
<eae> florian: A minimal test case would be good, but I'm fine with it.
<eae> Rossen: There is one in the github issue
<eae> rachelandrew: I'll add a test as part of spec change.
<eae> florian: I volunteer to review it.
<eae> RESOLVED: Apply proposed edit from Oct 2013 to spec.
Activity
rachelandrew commentedon Nov 6, 2017
An example so we can see how this currently behaves, use Firefox to see the overflowing item painted over the rule (existing clipping interop issue means you can't see that in other browsers) https://bugs.chromium.org/p/chromium/issues/detail?id=269061#c19
https://codepen.io/rachelandrew/pen/OOXYZY?editors=1100
I think this is just a straightforward edit, as it seems to be what browsers are doing anyway.
Relevant section of the spec: https://www.w3.org/TR/css-multicol-1/#column-gaps-and-rules
css-meeting-bot commentedon Nov 7, 2017
The Working Group just discussed
z-order of column-rule and column scrolling.The full IRC log of that discussion
<eae> Topic: z-order of column-rule and column scrolling<eae> github issue: https://github.com//issues/1739
css-meeting-bot commentedon Nov 7, 2017
The Working Group just discussed
Multicolumn issues, and agreed to the following resolutions:RESOLVED: Apply proposed edit from Oct 2013 to spec.The full IRC log of that discussion
<Rossen> Topic: Multicolumn issues<Rossen> github: https://github.com//issues/1739
<eae> rachelandrew: These first three issues are ones I dig out from the mailing list archive. They're all quite old.
<eae> rachelandrew: Things we've discussed, not sure what to do so brinng them up here.
<eae> rachelandrew: First one. z-order for column scrolling.
<eae> rachelandrew: Suggested change to wording.
<eae> rachelandrew: Is this something we want to add into the spec or do we need to dicuss it?
<eae> florian: Do we have interop on the proposed wording?
<eae> rachelandrew: There is an issue with overflow which as resolved a while ago, interop on the issue across browsers as far as I can tell.
<eae> rachelandrew: Firefox does not support spanning.
<eae> Rossen: Firefox is different due to that.
<eae> rachelandrew: Right, relating to the fact that thay haven't implemented it.
<eae> florian: The things that is linked to is not a minimized test case. Is an example.
<eae> rachelandrew: Correct.
<eae> Proposed resolution: Apply proposed edit from Oct 2013 to spec.
<bkardell_> sfbay
<eae> florian: A minimal test case would be good, but I'm fine with it.
<eae> Rossen: There is one in the github issue
<eae> rachelandrew: I'll add a test as part of spec change.
<eae> florian: I volunteer to review it.
<eae> RESOLVED: Apply proposed edit from Oct 2013 to spec.
[gap-decorations] Repaint scroll container rules after relayout