- From: Tobie Langel <tobie@fb.com>
- Date: Fri, 13 Sep 2013 16:57:20 +0200
- To: Zhang, Belem <belem.zhang@intel.com>
- CC: Tobie Langel <tobie@w3.org>, James Graham <james@hoppipolla.co.uk>, "public-test-infra@w3.org" <public-test-infra@w3.org>, "public-web-perf@w3.org" <public-web-perf@w3.org>
Can vendors easily build unprefixed version of their browser for internal testing?
--tobie
On Thursday, September 12, 2013 at 2:24 AM, Zhang, Belem wrote:
> 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 (mailto:public-test-infra@w3.org); public-web-perf@w3.org (mailto: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:57:47 UTC