MicrosoftEdge
/
webdriver
зеркало из
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
The WebDriver API and wire protocol
895 коммитов 7 Ветки 0 Теги 4,7 MiB
HTML 99%
JavaScript 0.9%
Shell 0.1%
Перейти к файлу
Simon Stewart 324b0724a1 Suggest browser specific extension in Protocol Extensions. (#326) 
This addresses the concern raised in #25418 by suggesting
that browser vendors include a product-specific part in the
extension prefix for protocol extensions.
 		2016-09-08 11:49:40 +01:00
graphics actually publishes resources to Echnida 2015-08-20 21:06:04 +01:00
.travis.yml publish on before_deploy since after_deploy isn't run if deploy isn't defined 2015-08-28 20:34:41 +01:00
README.md readme: remove validation step as this is automatic now 2015-08-07 14:59:06 +01:00
bug-assist.js bug-assist: use TLS link to W3C bug tracker 2015-02-12 20:48:56 +01:00
echidna-manifest.txt fix typo in Echnida manifest 2015-08-27 14:14:29 +01:00
validate validate: use https://validator.w3.org/nu/ as our validator 2015-08-07 14:44:45 +01:00
webdriver-spec.html Suggest browser specific extension in Protocol Extensions. (#326) 2016-09-08 11:49:40 +01:00

README.md

W3C WebDriver Specification Build Status

This repository contains the ongoing work on the W3C specification for the browser automation protocol known as WebDriver. It is being developed by the Browser Testing and Tools Working Group.

The working draft version of the spec is automatically re-published each time a change is committed to the editor’s draft. So the content of the two versions is identical, they just have slightly different presentational “skinning”.

Bugs can be filed against the W3C bug tracker, and pull requests should patch webdriver-spec.html.