Doesn't look like an issue, it will just expose a new flag which would provide version detection.
---------- Forwarded message ---------- From: Andreas Tolfsen ato@sny.no Date: Mon, Feb 5, 2018 at 10:37 AM Subject: Intent to implement and ship navigator.webdriver To: dev-platform dev-platform@lists.mozilla.org Cc: tools-marionette@lists.mozilla.org
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 authors a way to infer if user agent is controlled by automation, so the document can take alternate code paths when under test.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1169290
Standard: https://w3c.github.io/webdriver/webdriver-spec.html#interface
Estimated target release: 60
Testing: Covered by WPT.
Do other engines have this? Blink [1], Edge, and WebKit [2] have this. Blink only exposes the attribute during automation, but we expect them to unconditionally expose it given a recent specification change [3].
[1] https://groups.google.com/a/chromium.org/d/msg/blink-dev/6GysDZCWwB8/rXbGoRo... [2] https://git.webkit.org/?p=WebKit.git;a=commit;h=ce5ef8d5e72fb49cf2a0b72e2a5a... [3] https://github.com/w3c/webdriver/commit/a224627dcea6448367523bf0420de3d54794...
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform