W3C home > Mailing lists > Public > www-archive@w3.org > March 2017

Transition Request: WebDriver to Candidate Recommendation

From: Michael[tm] Smith <mike@w3.org>
Date: Thu, 9 Mar 2017 20:47:40 +0900
To: Tim Berners-Lee <timbl@w3.org>, "Ralph R. Swick" <swick@w3.org>, Philippe Le Hegaret <plh@w3.org>
Cc: David Burns <dburns@mozilla.com>, Simon Stewart <shs@rocketpoweredjetpants.com>, w3t-comm@w3.org, chairs@w3.org, www-archive@w3.org
Message-ID: <20170309114740.hunxqqxudegubwfh@sideshowbarker.net>
This is a request from the Browser Testing and Tools Working Group to
transition the WebDriver spec to Candidate Recommendation.

# Title: WebDriver
# URL: https://w3c.github.io/webdriver/webdriver-spec.html
# Estimated publication date: 16 March 2017

# Abstract:

WebDriver is a remote-control interface that enables introspection and
control of user agents. It provides a platform- and language-neutral wire
protocol as a way for out-of-process programs to remotely instruct the
behavior of web browsers.

Provided is a set of interfaces to discover and manipulate DOM elements in
web documents and to control the behavior of a user agent. It is primarily
intended to allow web authors to write tests that automate a user agent
from a separate controlling process, but may also be used in such a way as
to allow in-browser scripts to control a — possibly separate — browser.

# Status:


# Decision to request transition

Message from Browser Testing and Tools working group chair David Burns:


# Changes

https://github.com/w3c/webdriver/commits/master provides a complete change
history for the specification.

# Requirements satisfied

The primary requirement for this document is to document the WebDriver wire
protocol and Actions API, as well as its standard Capabilities, Sessions model,
and navigation behavior, along with details such as command contexts, and
element interaction, as currently supported in multiple implementations.

The success of the specification in meeting its requirement is attested to
by existing widespread usage of WebDriver.

# Dependencies met

There are no dependencies which have not been satisfied.

The spec has normative dependencies on the following W3C Recs:

* Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) (Rec)
* Page Visibility (Second Edition) (Rec)
* Pointer Events (Rec)
* Namespaces in XML 1.0 (Third Edition) (Rec)
* XML Path Language (XPath) Version 1.0 (Rec)

The spec has normative dependencies on the following W3C CRs:

* CSS Cascading and Inheritance Level 4 (CR)
* CSS Values and Units Module Level 3 (CR)
* Geometry Interfaces Module Level 1 (CR)

The spec has normative dependencies on the following W3C working drafts:

* Content Security Policy Level 3 (WD)
* CSS Device Adaptation Module Level 1 (WD)
* CSS basic box model (WD)
* CSS Display Module Level 3 (WD)
* CSS Object Model (CSSOM) (WD)
* CSSOM View Module (WD)
* DOM Parsing and Serialization (WD)
* HTML Editing APIs (WD)
* UI Events (WD)
* UI Events KeyboardEvent code Values (WD)
* UI Events KeyboardEvent key Values (WD)
* Web IDL (WD)

The spec has normative dependencies on the following WHATWG Living Standards:

* DOM (LS)
* Fetch (LS)
* URL (LS)
* Fullscreen API (LS)
* Infra (LS)

The Web Notification Working Group has responded to all review feedback
submitted by other groups, and all other groups remain satisfied with the
resolutions they have received for their comments.

# Wide review and issues addressed

The GitHub issue tracker for WebDriver has more than 200 resolved issues


# Formal objections


# Implementation

The group will produce an implementation report before transition out of CR.

# Patent disclosures

As attested to by the WebDriver Working Group Patent Policy Status page
https://www.w3.org/2004/01/pp-impl/49799/status there have been no patent
disclosures and no requests for exclusions.

Michael[tm] Smith https://sideshowbarker.net/

Received on Thursday, 9 March 2017 11:48:12 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 9 March 2017 11:48:13 UTC