From e9789bcd4524b5d082e0b44c0d0d757d5615c706 Mon Sep 17 00:00:00 2001 From: Jo Liss Date: Thu, 1 Sep 2011 21:05:17 +0200 Subject: [PATCH] Update README to reflect new :resynchronize default --- README.rdoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.rdoc b/README.rdoc index 6ca16796..9d9f1964 100644 --- a/README.rdoc +++ b/README.rdoc @@ -240,10 +240,9 @@ At the moment, Capybara supports {Selenium 2.0 *not* Selenium RC. Provided Firefox is installed, everything is set up for you, and you should be able to start using Selenium right away. -By default Capybara tries to synchronize Ajax requests, so it will wait for -Ajax requests to finish after you've interacted with the page. You can switch -off this behaviour by setting the driver option :resynchronize to -false. See the section on configuring drivers. +Capybara can wait for Ajax requests to finish after you've interacted with the +page. To enable this behaviour, set the :resynchronize driver option +to true. See the section on Asynchronous JavaScript for details. Note: Selenium does not support transactional fixtures; see the section "Transactional Fixtures" below. @@ -474,7 +473,8 @@ and {solution 3}[http://pastie.org/1745020]) for details. When working with asynchronous JavaScript, you might come across situations where you are attempting to interact with an element which is not yet present -on the page. Capybara automatically deals with this by waiting for elements +on the page. When the :resynchronize driver option is set to +true, Capybara automatically deals with this by waiting for elements to appear on the page. When issuing instructions to the DSL such as: