Re: Browser detection for shepherd/css test runner

On Mar 27, 2015, at 2:42 PM, Florian Rivoal <florian@rivoal.net> wrote:

> 
>> On 27 Mar 2015, at 22:09, Christian Biesinger <cbiesinger@google.com> wrote:
>> 
>> Hi there,
>> 
>> looking at the icons on
>> http://dev.w3.org/csswg/css-flexbox/#abspos-items, and test results
>> like http://test.csswg.org/harness/details/css-flexbox-1_dev/flexbox-abspos-child-001b/engine/webkit/,
>> it seems that the test runner considers Chrome to be Webkit.
>> 
>> That is bad. Chrome does not use Webkit anymore, and there is
>> definitely divergence between the two. Conversely, Presto is not so
>> important anymore.
>> 
>> Any chance of getting this updated?
> 
> 
> Completely agree with you with regards to Chrome.

The problem is, while there’s divergence in some areas, there’s still shared code in many (most?), and it currently requires human judgement to determine if passes form both count as two independent implementations or not.

If someone wants to generate a map (keyed by spec section) where there’s divergence (or the converse would be better, since that set isn’t getting bigger), I’d be happy to have the test harness automatically differentiate the results.

For the record, each result is keyed to the full UA string that generated it, so we can always go back and re-assign results to different products.

> 
> As for Presto, it is certainly of quickly declining relevance, but there are still a few areas where it supports features not supported in other browsers, or conforms better than other browsers. I think we should keep it for a while longer. As it provides useful information to the people working on the spec or the tests.
> 
> Besides, there's nothing wrong with a little tongue-in-cheek challenge to other browsers ("Even old Presto gets this right!”).

No reason to remove old passing implementations… I’ll take passes from Lynx if it helps get a spec to CR.