- From: François REMY via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Sep 2022 23:07:26 +0000
- To: public-css-archive@w3.org
My purpose for this discussion is two-folds: 1. Is the existence of an improved table spec sufficient to reassure implementers to attempt changes to their table layout behavior in well-scoped scenarios? a. If the answer is no, then I will go ahead and shelve this type of issue for now (move to css-tables-4). 2. If the answer is yes, would adding “gap” behavior to table be meaningful and desirable? a. One reason why it could be undesirable is that “gap” behavior would not insert spacing between the border of the table and the border of the first cells of the tracks. b. If the answer is no, then I will go ahead and close the issue. 3. If the answer is yes, we would be discussing details about the proposal: a. How to resolve percentages? - Should we only enable them on tables with explicit width and treat them as 0% otherwise? b. How to resolve the conflict with border-spacing? - Should the effects override each other? - Should the effects stack? -- GitHub Notification of comment by FremyCompany Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4848#issuecomment-1247388368 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 September 2022 23:07:28 UTC