- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Feb 2018 19:50:19 +0000
- To: public-css-archive@w3.org
Here I am again, taking turns with @rakuco to look into [a normative spec change without tests](https://docs.google.com/document/d/1kFYTqUMEbo9p87i6wAzORoicMWgHsuYwL2CgtvdhDaE/edit?usp=sharing) every week this quarter, to understand the challenges better. This week I landed on https://github.com/w3c/csswg-drafts/commit/7272dc55dee4ad563237fe1c750fe90f887c08d6 (a lot of commits in CSS, not randomly selected, but most other things I looked at were editorial, tested, or very new feautres) That links here. Curiously, there isn't even a css-sizing directory in https://github.com/w3c/web-platform-tests/tree/master/css, so I'm probably missing something important about the nature of this spec. Maybe what it says can only be tested indirectly through its effect on other specs? The word "must" isn't used much, at least. Anyway, https://github.com/w3c/csswg-drafts/commit/7272dc55dee4ad563237fe1c750fe90f887c08d6 *looks* like something for which it would be straightforward to write a test using `getComputedStyle` or reftests, to see that the resolved style is one thing, but its effect is another. Presumably such tests would all pass since it's for backwards compat. @dholbert, since you filed this issue, what do you think it'd take to determine whether this has been implemented or not, somewhere down the line? If this is actually a case that doesn't make sense to write tests for that's fine, I'd like to understand when that's the case too. -- GitHub Notification of comment by foolip Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2248#issuecomment-362381552 using your GitHub account
Received on Thursday, 1 February 2018 19:50:21 UTC