From e76942110b3eed0a61c47a4e844ded1f335bd6af Mon Sep 17 00:00:00 2001 From: Henning Koch Date: Fri, 22 Dec 2023 13:08:19 +0100 Subject: [PATCH] Fix typo in README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 10e68d6..bff8b9f 100644 --- a/README.md +++ b/README.md @@ -377,7 +377,7 @@ It is theoretically possible that your test will observe the browser in that win Any issues caused by this will usually be mitigated by Capybara's retry logic. **If** you think that this is an issue for your test suite, you can configure capybara-headless to wait additional tasks before it considers the browser to be idle: ```ruby -Capybara::Lockstep.wait_tasks = 2 // default is 1 +Capybara::Lockstep.wait_tasks = 2 # default is 1 ``` If you see longer chains of `then()` or nested `setTimeout()` calls in your code, you may need to configure a higher number of tasks to wait.