- From: Zhang, Belem <belem.zhang@intel.com>
- Date: Thu, 12 Sep 2013 00:24:56 +0000
- To: Tobie Langel <tobie@w3.org>, James Graham <james@hoppipolla.co.uk>
- CC: "public-test-infra@w3.org" <public-test-infra@w3.org>, "public-web-perf@w3.org" <public-web-perf@w3.org>
For vendor prefixes, do not include vendor prefixes when pushing tests to the W3C. But I have a questions here, some test cases borrows BrowserHasFeature() function which uses GetVendorPrefix workarounds, shall we remove such codes as well when pushing tests to W3C, I don't think the standard TC should include this? http://w3c-test.org/web-platform-tests/master/vibration/support/feature-detection.js function GetVendorPrefix(parent, feature, isAttribute) { //Known vendor prefixes var VendorPrefixes = ["moz", "ms", "o", "webkit"]; ... } Thanks, Belem -----Original Message----- From: Tobie Langel [mailto:tobie@w3.org] Sent: Wednesday, September 11, 2013 10:27 PM To: James Graham Cc: public-test-infra@w3.org; public-web-perf@w3.org Subject: Re: Use of prefixes in tests On Wednesday, September 11, 2013 at 4:23 PM, James Graham wrote: > Please don't add browser-specific features, including prefixes, to the > shared test repository, even if you make some attempt to be "fair" and > have one non-standard codepath per well-known implementation. Yes, please don't do this. --tobie
Received on Friday, 13 September 2013 14:47:33 UTC