- From: <bugzilla@jessica.w3.org>
- Date: Fri, 17 Mar 2017 10:50:58 +0000
- To: public-css-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30075 Bug ID: 30075 Summary: Visibility: collapse should cause a recalculation on affected rows with rowspan and affected columns with colspan (as applicable) Product: CSS Version: unspecified Hardware: All URL: https://www.w3.org/TR/CSS22/tables.html#dynamic-effect s OS: All Status: NEW Severity: minor Priority: P2 Component: CSS Level 2 Assignee: bert@w3.org Reporter: brunoaiss@gmail.com QA Contact: public-css-bugzilla@w3.org CC: bert@w3.org Target Milestone: --- Currently, with <tr>, (source: https://www.w3.org/TR/CSS22/tables.html#dynamic-effects ) When a <tr> has the CSS rule and a <td> has rowspan, the contents are supposed to be clipped. E.g.: For a table like this: +--------+-------+ | grp1 | info1 | | +-------+ | | info2 | | +-------+ | | info3 | +--------+-------+ | | info4 | | +-------+ | grp2 | info5 | | +-------+ | | info6 | +--------+-------+ | | info7 | | +-------+ | | info8 | | +-------+ | grp3 | info9 | +--------+-------+ grp1 is vertically-aligned to the top grp2 is vertically-aligned to the middle grp3 is vertically-aligned to the bottom ## According to the spec, for each of the below changes: "visibility:collapse" the first row of each span group, and it should become like this: +--------+-------+ | | info2 | | +-------+ | | info3 | +--------+-------+ | grp2 | info5 | | +-------+ | | info6 | +--------+-------+ | | info8 | | +-------+ | grp3 | info9 | +--------+-------+ "visibility:collapse" the second row of each span group, and it should become like this: +--------+-------+ | grp1 | info1 | | +-------+ | | info3 | +--------+-------+ | | info4 | | +-------+ | | info6 | +--------+-------+ | | info7 | | +-------+ | grp3 | info9 | +--------+-------+ "visibility:collapse" the 3rd row of each span group, and it should become like this: +--------+-------+ | grp1 | info1 | | +-------+ | | info2 | +--------+-------+ | | info4 | | +-------+ | grp2 | info5 | +--------+-------+ | | info7 | | +-------+ | | info8 | +--------+-------+ Issues: When working with text in tables, it can end up become unnecessarily clipped out when a row is hidden. Just see what happens above when the row where the text is is collapsed. There's still a lot of space available but the text just doesn't appear there because it was clipped out. Suggestion: When "visibility:collapsed" is applied to a row: 1: The cells' rowspan that span through the affected row will have their rowspan value deducted by 1. 2: All "blocks" inside cells that have had rowspan deducted and have rowspan over 0 will be repositioned inside the cell according to vertical-align property. The cell should not change size to accommodate the content. All content that does not fit the cell just by repositioning it should be clipped. For the above, the same ideology applies to columns. "visibility:collapse" the first row of each span group, and it should become like this: +--------+-------+ | grp1 | info2 | | +-------+ | | info3 | +--------+-------+ | | info5 | | grp2 +-------+ | | info6 | +--------+-------+ | | info8 | | +-------+ | grp3 | info9 | +--------+-------+ "visibility:collapse" the second row of each span group, and it should become like this: +--------+-------+ | grp1 | info1 | | +-------+ | | info3 | +--------+-------+ | | info4 | | grp2 +-------+ | | info6 | +--------+-------+ | | info7 | | +-------+ | grp3 | info9 | +--------+-------+ "visibility:collapse" the 3rd row of each span group, and it should become like this: +--------+-------+ | grp1 | info1 | | +-------+ | | info2 | +--------+-------+ | | info4 | | grp2 +-------+ | | info5 | +--------+-------+ | | info7 | | +-------+ | grp3 | info8 | +--------+-------+ Any Reasons why this is a bad idea or this won't work? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 17 March 2017 10:51:06 UTC