W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2017

[csswg-drafts] [all] Consider policy to ask for web-platform-tests

From: Simon Pieters via GitHub <sysbot+gh@w3.org>
Date: Wed, 23 Aug 2017 18:38:21 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-252377124-1503513493-sysbot+gh@w3.org>
zcorpan has just created a new issue for https://github.com/w3c/csswg-drafts:

== [all] Consider policy to ask for web-platform-tests ==
See https://github.com/w3c/fxtf-drafts/pull/215 for this for fxtf.

I would like to adopt this policy for cssom and cssom-view. Having tests and browser bugs for each normative spec change has turned out to be a really good way to reduce the time it takes for that change to be interoperably implemented, which is one of the main goals of standards.

We have lots of specs here. I don't know if this policy makes sense for all CSS specs. But I think it does for most of them. I would be happy to do this for only cssom and cssom-view for now, but I'd like the CSS WG to consider this for every spec, so we can decide what's best and apply that.

Case study: Chromium recently sent an [Intent to Implement and Ship for the 'q' unit](https://groups.google.com/a/chromium.org/d/msg/blink-dev/RRUYxYvsRCk/7VillBFrCAAJ), and found that there was only a test for it for `<img sizes>`, there was no CSS-specific test. With this policy, there would be some tests written and ideally also browser bugs filed asking to implement at the same time as it was added to the specification.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1755 using your GitHub account
Received on Wednesday, 23 August 2017 18:38:19 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:17 UTC