From a2d6ee874627f699b9b5884ba14306e8245a2195 Mon Sep 17 00:00:00 2001
From: Simon Coen <32054457+Siolto@users.noreply.github.com>
Date: Wed, 6 Apr 2022 13:58:51 +0200
Subject: [PATCH] fix: headless code example (#216)

* fix: use the correct chromeOptions code Example

* feat: extend the documentation about running headless mode
---
 docs/recipes.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/recipes.md b/docs/recipes.md
index d7a246f9..045f1c94 100644
--- a/docs/recipes.md
+++ b/docs/recipes.md
@@ -135,7 +135,7 @@ exports.config = {
       browserName: "chrome",
       acceptInsecureCerts: true,
       "goog:chromeOptions": {
-          ["window-size=1440,800", "--auto-open-devtools-for-tabs"] // <--
+        args: ["--window-size=1440,800", "--auto-open-devtools-for-tabs"] // <--
       }
     }
   ]
@@ -146,7 +146,7 @@ The browser will be started by `wdi5` with the DevTools immediately available.![
 
 ## Chrome: run headless
 
-"headless" means running the browser without a GUI.  
+"headless" means running the browser without a GUI. Running browsers in "headless" mode is a great way for running automated tests, especially in an continous integration pipeline.
 In `wdio.conf.(j|t)s`, provide "headless" as `args` to the `chrome` capability:
 
 ```js
@@ -161,14 +161,14 @@ exports.config = {
       browserName: "chrome",
       acceptInsecureCerts: true,
       "goog:chromeOptions": {
-          ["window-size=1440,800", "--headless"] // <--
+        args: ["--window-size=1440,800", "--headless"] // <--
       }
     }
   ]
 }
 ```
 
-Note that running headless can still be combined with a dedicated viewport, `1440,800` in the example above.
+However, there can be one problem: The "invisible" browser window starts a viewport only the size of 800x600, which is often too small for modern responsive applications. You can combine running headless with a dedicated viewport, `1440,800` like in the example above.
 
 ## DevX: code completion for `wdi5`- and `wdio`-API