diff --git a/index.html b/index.html index 9339a737..89b06a14 100644 --- a/index.html +++ b/index.html @@ -1,6 +1,6 @@ - + - +

WebDriver

-

W3C Editor's Draft

+

W3C Editor's Draft

More details about this document
@@ -606,7 +606,7 @@

WebDriver

The WebDriver protocol consists of communication between:

-
Local end +
Local end

The local end represents the client side of the protocol, which is usually in the form of language-specific libraries providing an API on top of the WebDriver protocol. @@ -1409,13 +1409,13 @@

WebDriver

where 1234 is not the session id of a session would return an HTTP response with the status 404 and a body of the form: - 

{
-	"value": {
-		"error": "invalid session id",
-		"message": "No active session with ID 1234",
-		"stacktrace": ""
-	}
-}
+ 

{
+	"value": {
+		"error": "invalid session id",
+		"message": "No active session with ID 1234",
+		"stacktrace": ""
+	}
+}

Certain commands may also annotate errors with additional error data. @@ -1424,13 +1424,13 @@

WebDriver

where the user prompt message may be included in a "text" field: - 

{
-	"value": {
-		"error": "unexpected alert open",
-		"message": "",
-		"stacktrace": "",
-		"data": {
-			"text": "Message from window.alert"
+ 
{
+	"value": {
+		"error": "unexpected alert open",
+		"message": "",
+		"stacktrace": "",
+		"data": {
+			"text": "Message from window.alert"
 		}
 	}
 }

@@ -1792,17 +1792,17 @@ 
WebDriver

  
An example new session request body
   might look like this:
 
- 
{
-  "capabilities": {
-    "alwaysMatch": {
+ 
{
+  "capabilities": {
+    "alwaysMatch": {
       // browser specific configuration
-      "<prefix>:browserOptions": {
-        "binary": "/usr/bin/browser-binary",
-        "args": ["--start-page=https://example.com"],
-      }
-    }
-  }
-}

+      "<prefix>:browserOptions": {
+        "binary": "/usr/bin/browser-binary",
+        "args": ["--start-page=https://example.com"],
+      }
+    }
+  }
+}

 
 
  
@@ -1829,11 +1829,11 @@ 
WebDriver

 
As an example, Mozilla could elect to hide new features behind capabilities
 with a "moz:" prefix:
 
-
{
-	"browserName": "firefox",
-	"browserVersion": "1234",
-	"moz:experimental-webdriver": true
-}

+
{
+	"browserName": "firefox",
+	"browserVersion": "1234",
+	"moz:experimental-webdriver": true
+}

 
 
 
@@ -2801,27 +2801,27 @@ 
WebDriver
extension capabilities specific to that implementation to an endpoint node,
  the following is also permitted by this specification:
 
- 
{
-    "capabilities": {
-        "alwaysMatch": {
-            "cloud:user": "alice",
-            "cloud:password": "hunter2",
-            "platformName": "linux"
-        },
-        "firstMatch": [
-            {"browserName": "chrome"},
-            {"browserName": "edge"}
-        ]
-    }
-}

+ 
{
+    "capabilities": {
+        "alwaysMatch": {
+            "cloud:user": "alice",
+            "cloud:password": "hunter2",
+            "platformName": "linux"
+        },
+        "firstMatch": [
+            {"browserName": "chrome"},
+            {"browserName": "edge"}
+        ]
+    }
+}
Once all capabilities are merged from this example,
   an endpoint node would receive New Session capabilities identical to:
 
- 
[
-    {"browserName": "chrome", "platformName": "linux"},
-    {"browserName": "edge", "platformName": "linux"}
-]

+ 
[
+    {"browserName": "chrome", "platformName": "linux"},
+    {"browserName": "edge", "platformName": "linux"}
+]
The remote end steps, given session, URL
@@ -3404,7 +3404,7 @@ 
WebDriver

   to https://example.com, the local end would POST
   to /session/1/url with the body:
 
- 
{"url": "https://example.com"}

+ 
{"url": "https://example.com"}
The remote end steps, given session, URL
@@ -5727,8 +5727,8 @@ 
WebDriver

 and uses this as the argument for a script it injects
 to remove it from the HTML document:
 
-
let body = session.find.css("#toremove");
-session.execute("arguments[0].remove()", [body]);
+
let body = session.find.css("#toremove");
+session.execute("arguments[0].remove()", [body]);
 

 
 
@@ -11469,13 +11469,13 @@ 
WebDriver

 as part of an additional "data" Object
 on the error representation:
 
-

+

 {
-	"error": "unexpected alert open",
-	"message": "implementation defined",
-	"stacktrace": "",
-	"data": {
-		"text": "the text from the alert"
+	"error": "unexpected alert open",
+	"message": "implementation defined",
+	"stacktrace": "",
+	"data": {
+		"text": "the text from the alert"
 	}
 }
 

@@ -14207,7 +14207,7 @@ 
WebDriver

     
[accname-1.1]

       Accessible Name and Description Computation 1.1. Joanmarie Diggs; Bryan Garaventa; Michael Cooper.  W3C. 18 December 2018. W3C Recommendation. URL: https://www.w3.org/TR/accname-1.1/
     
[CSP3]

-      Content Security Policy Level 3. Mike West; Antonio Sartori.  W3C. 18 June 2024. W3C Working Draft. URL: https://www.w3.org/TR/CSP3/
+      Content Security Policy Level 3. Mike West; Antonio Sartori.  W3C. 9 September 2024. W3C Working Draft. URL: https://www.w3.org/TR/CSP3/
     
[CSS-CASCADE-4]

       CSS Cascading and Inheritance Level 4. Elika Etemad; Tab Atkins Jr..  W3C. 13 January 2022. W3C Candidate Recommendation. URL: https://www.w3.org/TR/css-cascade-4/
     
[CSS-DEVICE-ADAPT]

@@ -14285,7 +14285,7 @@ 
WebDriver

     
[UAX44]

       Unicode Character Database. Ken Whistler.  Unicode Consortium. 6 September 2023. Unicode Standard Annex #44. URL: https://www.unicode.org/reports/tr44/tr44-32.html
     
[UI-EVENTS]

-      UI Events. Gary Kacmarcik; Travis Leithead.  W3C. 22 June 2024. W3C Working Draft. URL: https://www.w3.org/TR/uievents/
+      UI Events. Gary Kacmarcik; Travis Leithead.  W3C. 7 September 2024. W3C Working Draft. URL: https://www.w3.org/TR/uievents/
     
[UIEVENTS-KEY]

       UI Events KeyboardEvent key Values. Travis Leithead; Gary Kacmarcik.  W3C. 30 May 2023. W3C Candidate Recommendation. URL: https://www.w3.org/TR/uievents-key/
     
[Unicode]

@@ -14489,7 +14489,7 @@ 
WebDriver

       
       

         Permalink
-         
+        exported 
       

       
Referenced in: