- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Nov 2022 15:57:21 +0000
- To: public-css-archive@w3.org
@tabatkins and I follow the formatting outlined in https://lists.w3.org/Archives/Public/spec-prod/2018OctDec/0011.html - [Phrase-based semantic line breaks](https://rhodesmill.org/brandon/2012/one-sentence-per-line/) - Tabs for indentation, spaces for alignment - Indent the entire spec one level except for headings, so sections are easy to pick out - Further indent the contents of block-level HTML elements except P, per standard HTML indentation practice - Empty lines between blocks - No optional end tags, because they're noisy. We don't particularly care whether someone else's spec is using spaces or tabs for indentation, so long as it's consistent. We understand that some people don't know how to use tabs vs spaces properly, or have bad text editors, so using spaces only makes sense for them even though it's an inferior system. :P However using tabs for alignment is not acceptable, since that breaks if someone else's text editor sets them to a different value. Likewise mixing tabs and spaces for indentation. We care a lot about using [semantic line breaks](https://rhodesmill.org/brandon/2012/one-sentence-per-line/). You'll see that in the source code of every modern spec we edit: Grid, Flexbox, Alignment, Text, Box, Selectors, Values, Cascade, etc. etc. etc. Note: css-grid-3 was drafted by Mats Palmgren as a masonry layout proposal; if you want to see how Grid is formatted, look at level 1 or 2. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8000#issuecomment-1302324608 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 15:57:22 UTC