Re: New Session parameters

This sounds like a good way to enable engine features / integrations programmatically, such as opening the developer tools or turning on the JS debugger. Although, none of these things are “capabilities” in the sense that they are either supported or not. So they don’t make sense as “required capabilities” and shouldn’t be interpreted by intermediary nodes.

Brian

> On May 27, 2016, at 2:13 PM, Clay Martin <clmartin@microsoft.com> wrote:
> 
> We are currently investigating allowing experimental flags to be set via capabilities, just a thought.
> 
> -----Original Message-----
> From: James Graham [mailto:james@hoppipolla.co.uk] 
> Sent: Friday, May 27, 2016 5:54 AM
> To: public-browser-tools-testing@w3.org
> Subject: Re: New Session parameters
> 
> Irrespective of the discussion about desired and required capabilities, I would like to standardise a subset capabilities/parameters that can be provided to browsers corresponding to the items likely to be used by more than one browser. In particular, I am thinking:
> 
> args - command line arguments
> binary - browser binary
> profile - a base64 encoded profile to use?
> [others?]
> 
> Obviously there would still be browser-specific settings, but standardising common ones is useful because it allows new browsers to work with existing webdriver clients without having to write substantive browser-specific code in the client.
>

Received on Thursday, 2 June 2016 02:08:30 UTC