- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Apr 2018 09:30:05 +0000
- To: public-css-archive@w3.org
Yes, if we the spec stays unchanged, it's a bug in Chrome, [we reject for <= 0, should be easy to fix by changing the parse-time check](https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/css/properties/css_parsing_utils.cc?type=cs&sq=package:chromium&l=1567). It's a different discussion how much sense is in 0% as a stretch value. -- GitHub Notification of comment by drott Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2591#issuecomment-382325224 using your GitHub account
Received on Wednesday, 18 April 2018 09:30:10 UTC