W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2018

Re: [csswg-drafts] [css-multicol] column rules should only be drawn to the height of the column contents

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 28 Feb 2018 17:35:08 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-369318312-1519839306-sysbot+gh@w3.org>
The Working Group just discussed `. [css-multicol] column rules should only be drawn to the height of the column contents`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: . [css-multicol] column rules should only be drawn to the height of the column contents<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2309<br>
&lt;dael> Rossen_: This came from dbaron a couple weeks ago and added by rachelandrew .<br>
&lt;dael> dbaron: There was a thing in the spec, I had been doing testing and it didn't match FF and CHrome and didn't make sense to me. Edge does impl what hte spec says. Question is what happens to column rules when content of columns doesn't fill the space it could fill<br>
&lt;Rossen_> test case: https://w3c-test.org/css/css-multicol/multicol-breaking-001.html<br>
&lt;dael> dbaron: Either because you have a multi-col with a spec width and height unspec # col. Depending on column-fill balance|auto you might have content in the first and second or the top of the first. Question is where do you draw the rules.<br>
&lt;dael> dbaron: Spec says a full height rule between any pair with content in them. Completely empty is no rule. THat's not what FF and Chrome do. Last comment in GH issue I linked to a test.<br>
&lt;dael> dbaron: I think it...don't look in FF, look in Chrome and Edge.<br>
&lt;dael> Rossen_: I'm assuming you're going to be fixing in FF, that's why you're looking?<br>
&lt;dael> dbaron: What a moment...I think I've gotten things confused.<br>
&lt;dael> s/What/Wait<br>
&lt;dael> dbaron: FF has a bunch of other bugs here that are messing this up in weird ways.<br>
&lt;dael> dbaron: What htis test shows is a multicol inside another.<br>
&lt;dael> dbaron: Spec calls for the purple column to go all the way tot the bottom in the second column. FF &amp; CHrome only take it to the bottom of the content.<br>
&lt;dael> Rossen_: What is wrong with this? I believe what the spec suggests in terms of behavior as well as what IE/Edge/Presto impl for column rules makes a lot of sense.<br>
&lt;dael> Rossen_: Are you suggesting only make app column rules only draw to content type?<br>
&lt;dael> dbaron: That's what I'm suggesting. I made that suggestion before testing edge so I made it before realizing current browsers did the thing the spec said.<br>
&lt;dael> dauwhe: I perfer Chrome to the spec<br>
&lt;dael> dauwhe: Pruely as a visual thing, having the rule extend past empty space strikes me as unexpected.<br>
&lt;dael> plinss: I think it should be an author rule. Having rules only to content seems common, but you might want rules to go all the way when you're doing something sophisticated. If you're going to content you should make sure all rules are to the same length<br>
&lt;dael> dbaron: Makes sense for balancing, but not column fill auto.<br>
&lt;dael> dauwhe: I agree with plinss about author control though.<br>
&lt;dbaron> s/Makes sense/Might make sense/<br>
&lt;AmeliaBR> Does anyone have the current spec text? Is it really supposed to apply to columns inside columns?<br>
&lt;dael> Rossen_: To answer AmeliaBR, columns inside of columns brings nothing interesting. dbaron did it for illistrative purposes to show when the multicol itself is the content of another column what the behavior is.<br>
&lt;dbaron> AmeliaBR, the spec text is quoted in the first comment of the issue<br>
&lt;dael> Rossen_: In this case I would have expected that...if we have content height as the limit to column gaps, what Chrome does is the behavior which would be compliant. And if column rules are used to show where columns are and their height, because as dbaron illustrates when you have a background you'll see the heights, that looks just as silly as the other way where you don't have the BG but you have the rule.<br>
&lt;dael> Rossen_: I sympathize to plinss suggestion of an author control. Having the background &amp; the column rules not be the same height is pretty silly. THat's my personal opinion.<br>
&lt;dael> Rossen_: It seems strange that the two are not going hand in hand.<br>
&lt;dael> AmeliaBR: I brought it up because it seems browsers are consistant with outer level being full height. It's only when you add the inner level and how it break accross multiple it's weird<br>
&lt;dael> Rossen_: THe multicol inside the top level extends all the way down. That's why the rules are they way they are. It is visually deciving.<br>
&lt;dael> Rossen_: In this case if you had max-height on the inner and height on the outer so it stretches beyond I would expect column rules to be the same height<br>
&lt;dbaron> I'd note that if you remove the .outer { column-fill: auto } in the testcase than the thick blue rules get shorter<br>
&lt;dael> liam: There's a danger here that...in trying to decide based on weird test cases. If I had spec a height explicitly I'd expect the rule to go all the way down. Either you want a control as plinss said or it should honor the height if you gave one. Maybe you need to look at actual use cases.<br>
&lt;dael> Rossen_: Now you're suggesting tie in column height and rule properties which goes against our groups<br>
&lt;dael> liam: No no, I'm askign what is user's expectation. if you have an area with the height and column rules chances are you want the rules all the way donwn. I'm supporting a property.<br>
&lt;dael> Rossen_: I can't speak for the billions of users of the web. From a pure layout PoV what I said is if you ahev column boxes with backgrounds that exend the rules should extend the same way. THat's consistant with other properties.<br>
&lt;dael> Rossen_: Let's see if we can narrow down this issue and get to something actionable.<br>
&lt;dbaron> I think this was also a case where this was implemented in browsers *before* the current spec text existed.<br>
&lt;dael> Rossen_: Current proposal a 1) make a user control so people can explicitly control height of column rules to be that of the content height or the multicol height<br>
&lt;dael> Rossen_: 2) Stay with current spec which suggests height fo column rules is the same as the multicol element height<br>
&lt;dael> Rossen_: 3) Height of the column rule is based on height of the content fo the multi-height<br>
&lt;dael> Rossen_: We can try to make a resolution or we can stop discussing here and continue on GH. Get user feedback from designers, come back and see what stands out.<br>
&lt;dael> Rossen_: Preference dbaron ?<br>
&lt;dael> dbaron: I'm fine discussing more.<br>
&lt;dael> Rossen_: Okay.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2309#issuecomment-369318312 using your GitHub account
Received on Wednesday, 28 February 2018 17:35:10 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:46 UTC