W3C home > Mailing lists > Public > public-browser-tools-testing@w3.org > July to September 2015

Re: Specifying spec level in session

From: David Burns <dburns@mozilla.com>
Date: Thu, 20 Aug 2015 20:59:51 +0100
Message-ID: <CAAoW2AG9bM52J8tcW=fyX3xZe3mZYoOGYhoK2Eg2O=n-QK8JqQ@mail.gmail.com>
To: Jim Evans <james.h.evans.jr@gmail.com>
Cc: "public-browser-tools-testing@w3.org" <public-browser-tools-testing@w3.org>
I have added this to the specifcation in
https://github.com/w3c/webdriver/commit/3112d98a1f7f2f6fd5093c8eff52d8f04005560c

David

On 4 August 2015 at 22:27, David Burns <dburns@mozilla.com> wrote:

> I quite like this. It gives the client bindings authors a chance to throw
> necessary errors before calls are made and makes support levels an explicit
> thing rather than trying to sniff packets (which can be done for the
> OSS->L1) now but may not actually give us what we need in the future.
>
> David
>
> On 4 August 2015 at 22:21, Jim Evans <james.h.evans.jr@gmail.com> wrote:
>
>> I think it might be useful for local end language bindings to be able to
>> determine the level of the protocol being spoken by the remote end when a
>> session is created. To that end, it might be interesting to have the
>> specification level documented in the capabilities returned by the new
>> session command.
>>
>> My proposal would be to add a "specificationLevel" entry to the set of
>> "server capabilities" listed in the "Processing Capabilities" algorithm of
>> section 4. A compliant remote end must set the value of this capability to
>> 1 for remote ends adhering to the current version of the spec. When level 2
>> of the WebDriver spec is completed, compliant remote ends must set the
>> value to 2, and so on.
>>
>> Thoughts?
>>
>> --Jim
>>
>
>
Received on Thursday, 20 August 2015 20:00:20 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 20 August 2015 20:00:21 UTC