Re: Intent to implement and ship navigator.webdriver

Also sprach Andreas Tolfsen: > Summary: > I intend to implement and ship a new enumerable, configurable, > read-only "webdriver" attribute on the Navigator object. The > attribute is true when the -marionette flag is passed to Firefox > or the marionette.enabled preference is true. Otherwise it

Re: Intent to implement and ship navigator.webdriver

Also sprach Martin Thomson: > On Tue, Feb 6, 2018 at 3:37 AM, Andreas Tolfsen wrote: >> Motivation: >> To give web authors a way to infer if user agent is controlled by >> automation, so the document can take alternate code paths when under >> test. > > Can you speak more about why

Re: Intent to implement and ship navigator.webdriver

Also sprach Boris Zbarsky: > And in particular, the implementation patches don't match the intent > description (e.g. we implement a configurable property) Making it unforgeable is obviously a rather bad idea. I did mean that the attribute is _configurable_.

Re: Intent to implement and ship navigator.webdriver

Also sprach Boris Zbarsky: > On 2/5/18 11:37 AM, Andreas Tolfsen wrote: >> Standard: >> https://w3c.github.io/webdriver/webdriver-spec.html#interface > > All the IDL snippets in this standard are empty, which makes it > hard to evaluate the standard or how our implementation aligns with > it.

Re: Intent to implement and ship navigator.webdriver

On Tue, Feb 6, 2018 at 3:37 AM, Andreas Tolfsen wrote: > Motivation: > To give web authors a way to infer if user agent is controlled by > automation, so the document can take alternate code paths when under > test. Can you speak more about why this is a good idea? I've poor

Re: Intent to implement and ship navigator.webdriver

On 2/5/18 11:37 AM, Andreas Tolfsen wrote: Standard: https://w3c.github.io/webdriver/webdriver-spec.html#interface All the IDL snippets in this standard are empty, which makes it hard to evaluate the standard or how our implementation aligns with it. -Boris

Re: Intent to implement and ship navigator.webdriver

On 2/5/18 11:47 AM, Boris Zbarsky wrote: All the IDL snippets in this standard are empty, which makes it hard to evaluate the standard or how our implementation aligns with it. And in particular, the implementation patches don't match the intent description (e.g. we implement a configurable

Intent to implement and ship navigator.webdriver

Summary: I intend to implement and ship a new enumerable, non-configurable, read-only "webdriver" attribute on the Navigator object. The attribute is true when the -marionette flag is passed to Firefox or the marionette.enabled preference is true. Otherwise it is false. Motivation: To give web