- From: Tim Reichen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Aug 2020 04:27:49 +0000
- To: public-css-archive@w3.org
# Response to 1. The goal would be the parser to behave the same, with and without semicolons. This is possible with a simple rule as described above. # Response to 2. > Forgetting a semicolon at the end of a line is an easy mistake to make, so lots of people have made it. With this proposal, it would not be a mistake anymore. Concerning future css written code, I think it speaks more for this feature than against it. > Moreover, when a page doesn't quite look the way the author expected, a common strategy is to write more CSS rules until it does, rather than trying to understand why the existing rules do not create the expected result. I see what you mean. But changes on sites would only occur, if the css was invalid with the current specs in the first place. But css is changing all the time. Let's assume somebody wrote a property name in the past that was ignored by the specs at the time and it was implemented as a feature in css afterwards: That also potentially changes/breaks sites. So I don't agree we should show consideration for invalid css in that manner, else css would not be allowed to implement any new features/properties. -- GitHub Notification of comment by timreichen Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5413#issuecomment-674648468 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 17 August 2020 04:27:51 UTC