Re: [csswg-drafts] [css-tables] visibility: collapse

This [was discussed](https://log.csswg.org/irc.w3.org/css/2017-08-03/#e843904) at our face-to-face meeting at the beginning of this month, but didn't get linked back to this github issue.

**RESOLVED: cells spanning collapsed rows/columns are clipped to their resulting bounds (in both axes)**

<details>
<summary>Expand for the full IRC log</summary>
&lt;fantasai> topic: visibility collapse: clip or not to club
<br>&lt;fantasai> s/club/clip
<br>&lt;fantasai> gregwhitworth: Talked about this at TPAC
<br>&lt;fantasai> gregwhitworth: Specified Edge behavior currently
<br>&lt;fantasai> gregwhitworth: To not get rid of data
<br>&lt;fantasai> gregwhitworth: But when author asks for visibility collapse on column or row
<br>&lt;fantasai> gregwhitworth: They've asked that row or column to be gone
<br>&lt;fantasai> gregwhitworth: If you have a spanning cell that goes into the collapsed column/row, then clipped to visible columns/rows
<br>&lt;fantasai> fantasai: I think that's what's in the spec. Not really that great
<br>&lt;fantasai> gregwhitworth: FF overflows the content
<br>&lt;fantasai> gregwhitworth: Behind a flag in Chrome
<br>&lt;fantasai> dgrogan: We also clip to border box. Behind a flag
<br>&lt;fantasai> fantasai: I thin there were two options we were considering here, and overflowing was definitely not one of them
<br>&lt;fantasai> fantasai: ...
<br>* fantasai continues to ignore her comments
<br>&lt;fantasai> dbaron: This would ...
<br>* fantasai doesn't have anything to say worth minuting
<br>&lt;gregwhitworth> https://jsfiddle.net/v23h0338/
<br>&lt;fantasai> gregwhitworth explain the demo
<br>&lt;fantasai> dbaron: Suppose before collapsing ou have a cell here and it's part of 3 rows that are conceptually here
<br>&lt;fantasai> dbaron: cell has some content which overflows in theses various directions
<br>&lt;fantasai> dbaron: And then you collapse the middle one
<br>&lt;fantasai> dbaron: When it's not collapsed, these overflow visibly
<br>&lt;fantasai> dbaron: Are you saying when its collapsed, we only draw...
<br>&lt;fantasai> dbaron: I'm collapsing the middle row
<br>&lt;fantasai> gregwhitworth: You only draw what's in the first / third cells
<br>&lt;fantasai> [drawing on whiteboard, behind Bert, can't be captured for minutes]
<br>&lt;fantasai>  fremy: If you're clipping the middle row, do you draw the content in  the 1st and 3rd rows, or do you show the 1st and 2nd rows and clip out  the end
<br>&lt;fantasai>  dbaron: Once you collapse the middle row, you're clip everything that  overflows the top and you're clip out stuff [over there, over there  nobody is telling me what that means and I can't see it]
<br>&lt;fantasai> gregwhitworth: This is an edge case
<br>&lt;fantasai> gregwhitworth: Haven't seen people hiding rows/cols except in data grids, and ...
<br>&lt;fantasai> gregwhitworth: What you're proposing is complicated
<br>&lt;fantasai> dbaron: If it's not a use case why clip anything?
<br>&lt;fantasai> Rossen: That is the use case
<br>* fantasai wants a link to the previous minutes
<br>&lt;fantasai> Rossen: Your primary purpose was to have a layout
<br>&lt;fantasai> Rossen: We go to extreme lengths to avoid overflow
<br>&lt;fantasai> Rossen: To make sure that all content is displayed inall cells
<br>&lt;fantasai> Rossen: Then you have user facing behavior that allow ppl to collapse things away, purposefully make things appear or disappear
<br>&lt;fantasai> Rossen: When they explictily aske for something to disapear, and you continue to show them what disappeared, weird no?
<br>&lt;fantasai> dbaron: I just meant don't clip this cell
<br>&lt;fantasai> gregwhitworth: In dbaron's example ...
<br>&lt;gregwhitworth> https://jsfiddle.net/dgrogan/9uduq99L/3/
<br>&lt;fantasai> gregwhitworth: If you collapse
<br>&lt;fantasai> gregwhitworth: we end up clipping in both axes
<br>&lt;fantasai> gregwhitworth: My statement ot dbaron is, he forcefully asked for no wraps which will overflow
<br>&lt;fantasai> gregwhitworth: I don't see circumstances where it isn't primariy the excel-based scenario
<br>&lt;fantasai> gregwhitworth: this is the most performant way to accomplish, which is clipping to bounding box
<br>&lt;fantasai> gregwhitworth: weird side effect
<br>&lt;fantasai> dbaron: Proposal is that if you have a cell that spans some collapsed rows or columns
<br>&lt;fantasai> dbaron: that cell clips its content to its resulting bounds
<br>&lt;fantasai> gregwhitworth: yes
<br>&lt;fantasai> RESOLVED: cells spanning collapsed rows/columns are clipped to their resulting bounds
<br>&lt;fantasai> (in both axes)
<br>&lt;fantasai> Rossen: Goal of work on this spec is to minimize interop pain
<br>&lt;fantasai> Rossen: not trying to rewrite history
<br>&lt;fantasai> Rossen: issues aren't introduced, we're trying to write out the path of least resistance
<br>* fantasai found the minutes to last time we discussed
<br>&lt;fantasai> https://lists.w3.org/Archives/Public/www-style/2016Nov/0069.html
</details>

-- 
GitHub Notification of comment by dbaron
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/478#issuecomment-324492817 using your GitHub account

Received on Wednesday, 23 August 2017 23:44:27 UTC