- From: Tim Reichen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Aug 2020 19:41:32 +0000
- To: public-css-archive@w3.org
Agreed, scss is prefered, but afaik not because it uses semicolons to close declarations but because provided some other reasons ([article](http://thesassway.com/editorial/sass-vs-scss-which-syntax-is-better)). Also it tries to stay close to the standard which is css, so kinda of a circular argument for this proposal. I also agree that css should not go by indentation like sass or stylus to omit semicolons. # About JS I know what you mean. The ```return``` of nothing in js is weird, but I think that is not a problem with semicolons/newlines but the fact that JS doesn't have obligatory return values and interprets a single line ```return``` like ```return undefined```. CSS thankfully doesn't do anything like that. # Simple rule How about: In a block a```ident-token``` is followed by a ```:```. All subsequent tokens are ```Component value``` until the next ```ident-token```. -- GitHub Notification of comment by timreichen Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5413#issuecomment-671550148 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 August 2020 19:41:34 UTC