- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Nov 2022 12:25:35 +0000
- To: public-css-archive@w3.org
jakearchibald has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-view-transitions-1] Spec formatting == I think we should decide on: - Indenting level in code samples - Indenting level in the spec - Wrapping system ## Indenting level in the spec We're mostly using 4 spaces right now. The CSS grid and flexbox specs seem to use. The flexbox and grid specs seem to use tabs. **Recommendation:** Happy to follow working group preference here. Is that tabs? ## Indenting level in code samples Currently, we're inconsistent. Sometimes it's 2 spaces, 4 spaces, or even 6 spaces. For comparison, https://drafts.csswg.org/css-flexbox-1/ is mostly 2 spaces, but sometimes 4 and even sometimes 3. **Recommendation:** I'd rather do whatever we do for general spec indenting. I'm happy to use tabs for block indenting and spaces for alignment. If we use tabs, I'd like to use `tab-size: 2` in the spec CSS. ## Wrapping system Currently, we're inconsistent. https://github.com/w3c/csswg-drafts/blob/main/css-grid-3/Overview.bs is mostly no-hard-wrapping. https://github.com/w3c/csswg-drafts/blob/main/css-flexbox-1/Overview.bs seems to be semantic line breaks. **Recommendation:** My personal preference is no-hard-wrapping, and keep paragraphs short. However, I'm happy with semantic line breaks too. My only strong feeling is we should avoid breaking at an arbitrary char count, especially if that breaks referenced terms across lines, making it hard to search for particular terms. @fantasai happy for you to lay down the law here. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8000 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 November 2022 12:25:37 UTC