capybara 3.35.0 → 3.40.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 00bf1cfd1e72093422fb61df1dae86d72948e8026d57fb00084d5bedceb0967e
-  data.tar.gz: 65a8c6b66d1ef91586ca39f7eabcf800019f853e33e087d1bb65f02a85140c8b
+  metadata.gz: e0537a83e6809595a8e15b9c450f4f4b0976c5ebf1327cc0611ae20a05b3574b
+  data.tar.gz: c3035e7a05874cc93ab27c6aea26e529dea4c3b63bd5d3281deaaf34c45a91b0
 SHA512:
-  metadata.gz: f961de052aa75cb3e3a941ea031d40d6d0f1fc2a9a80190c7dbe2f7d8e96b462fa71d4ed96d4dc45687e2baaf151579ca4508a2753a6e2073814857e2dee9bb4
-  data.tar.gz: 4b02c84f7bd1d9da419e3f43848da87290ba303541df516e6217fd3fc2e4cf5263e212e9a4a5329c8505b2f6111c0ce6ea17537ea3099b04f12c9b662d364088
+  metadata.gz: 48c7bc5cbfc8e3324ea09d937a207299ad91ffc2e255dbbb7ed13265e4541c3672271ccb2f19b3902588d5c649cb6f561b7c483e7b815b824ccf37df8bbb5075
+  data.tar.gz: 5b3a9cc9a6ba6ed67a54ef381c00ed9cc94027d26bdfc98ba1c509a097c9dc123d39bd72a6a5728e5b5b4e503202e475889d22cf47c07ce88eb7afedf604ed83

data/History.md

@@ -1,5 +1,169 @@
+#Version 3.40.0
+Release date: 2024-01-26
+
+### Changned
+
+* Dropped support for Ruby 2.7, 3.0+ is now required
+* Dropped support for Selenium < 4.8
+* Use the new headless option on chromedriver with registered selenium driver [Neil Carvalho]
+
+### Added
+
+* `Capybara::Result#to_ary` to support multiple assignment [Sean Doyle]
+* `has_element?` and related matchers [Sean Doyle]
+*  Rack 3 support
+
+### Fixed
+
+* Forward save_screenshot options to selenium - Issue 2738
+* Rack test - don't auto submit forms with multiple inputs [Mitchell Henke]
+* Table row selector matches cell values in order - Issue 2686 [Jeff Parr]
+* Table row selector fixes for first column - Issue 2685 [Jeff Par]
+
+# Version 3.39.2
+Release date: 2023-06-10
+
+### Fixed
+
+* Fix Selenium version comparison [aki77]
+
+# Version 3.39.1
+Release date: 2023-05-12
+
+### Fixed
+
+* Fix usage of Selenium logger
+
+# Version 3.39.0
+Release date: 2023-04-02
+
+### Added
+
+* Support `:target` filter option on `:link` selector [Yudai Takada]
+* Experimental Rack 3 support
+* Text normalization performance improvements [Brandon Weaver]
+
+### Fixed
+
+* MS Edge button click [Brian J. Bayer]
+* Options/Capabilities choosing based on Selenium versions
+* Support for base versions [Matijs van Zuijlen]
+* ExpectedError not defined in Selenium 4+
+* Filter block forwarding to a number of matchers [Christophe Bliard]
+###  Changed
+
+* Dropped support for rack 1.x
+
+# Version 3.38.0
+Release date: 2022-11-03
+
+### Changed
+
+* Capybara.w3c_click_offset now defaults to true. If you need click offsets to be from the elements top left corner set it to false in your config
+
+### Added
+
+* Support Selenium 4.3 changes to click offset calculations
+* `click`, `double_click`, `right_click` can now be called on the session to click the currently scoped element (or document)
+* `Session#within` now passes the scoped element to the block
+* Support rack-test 2+
+* Retry interval is now configurable [Masahiro NOMOTO]
+* Support Puma 6 - Issue #2590
+* Selenium: DetachedShadowRootError is treated as an invalid element error [Perryn Fowler]
+* Selenium: When inspected shadow roots will have a tag name of "ShadowRoot"
+* `evaluate_async_script` added to Session::DSL_METHODS [Henry Blyth]
+
+### Fixed
+
+* Use higher precision clock in Capybara::Helpers::Timer if available
+* rack-test driver behavior with \r\n - Issue #2547 [Stefan Hoffmann]
+* Updated for deprecation of positional parameters in Selenium::WebDriver::ActionBuilder#pause
+* Explicitly set cause on server raised errors
+* Options no longer duplicated in have_xxx invalid option error message [Yudai Takada]
+* Animation disabler is now threadsafe [Daniel Sheppard]
+* Server connection count tracking [Oleksandr K.]
+* Ensure scopes are reset when session is [Henry Blyth]
+
+# Version 3.37.1
+Release date: 2022-05-09
+
+### Fixed
+
+* Regression in rack-test visit - Issue #2548
+
+# Version 3.37.0
+Release date: 2022-05-07
+
+### Changed
+
+* Ruby 2.7.0+ is now required
+
+### Added
+
+* [Beta] CSP nonces inserted into animation disabler additions - Issue #2542
+* Support `<base>` element in rack-test driver - ISsue #2544
+* [Beta] `Element#shadow_root` support. Requires selenium-webdriver 4.1+. Only currently supported with Chrome when using the selenium driver. Note: only CSS can be used to find elements from the shadow root. Therefore you won't be able to use most Capybara helper methods (`fill_in`, `click_link`, `find_field`, etc) directly from the shadow root since those locators are built using XPath. If you first locate a descendant from the shadow root using CSS then you should be able to use all the Capybara methods from there.
+* Regexp now supported for `exact_text` finder option
+
+### Fixed
+
+* Fragments in referer headers in rack-test driver - Issue #2525
+* Selenium v4.1 deprecation notice
+
+# Version 3.36.0
+Release date: 2021-10-24
+
+### Changed
+
+* Ruby 2.6.0+ is now required
+* Minimum selenium-webdriver supported is now 3.142.7
+
+### Added
+
+* Support for selenium-webdriver 4.x
+* `allow_label_click` accepts click options to be used when clicking an associated label
+* Deprecated `allow_gumbo=` in favor of `use_html5_parsing=` to enable use of Nokogiri::HTML5 when available
+* `Session#active_element` returns the element with focus - Not supported by the `RackTest` driver [Sean Doyle]
+* Support `focused:` filter for finding interactive elements - Not supported by the `RackTest` driver [Sean Doyle]
+
+### Fixed
+
+* Sibling and ancestor queries now work with Simple::Node - Issue #2452
+* rack_test correctly ignores readonly attribute on specific input element types
+* `Node#all_text` always returns a string - Issue #2477
+* `have_any_of_selectors` negated match - Issue #2473
+* `Document#scroll_to` fixed for standards behavior - pass quirks: true if you need the older behavior [Eric Anderson]
+* Use capture on attach file event listener for better React compatibility [Jeff Way]
+* Animation disabler produces valid HTML [Javi Martin]
+
+### Removed
+
+* References to non-w3c mode in drivers/tests. Non-w3c mode is obsolete and no one should be using it anymore. Capybara hasn't been testing/supporting it in a while
+
+# Version 3.35.3
+Release date: 2021-01-29
+
+### Fixed
+
+* Just a release to have the correct dates in the History.md in released gem
+
+# Version 3.35.2
+Release date: 2021-01-29
+
+### Fixed
+
+* Selenium deprecation suppressor with Selenium 3.x
+
+# Version 3.35.1
+Release date: 2021-01-26
+
+### Fixed
+
+* Default chrome driver registrations use chrome - Issue #2442 [Yuriy Alekseyev]
+* 'Capybara.test_id' usage with the :button selector - Issue #2443
+
 # Version 3.35.0
-Release date: 2020-01-25
+Release date: 2021-01-25
 
 ### Added
 
@@ -732,7 +896,7 @@ Release date: 2018-03-23
 
 ### Changed
 
-* Visibile text whitespace is no longer fully normalized in favor of being more in line with the WebDriver spec for visible text
+* Visible text whitespace is no longer fully normalized in favor of being more in line with the WebDriver spec for visible text
 * Drivers are expected to close extra windows when resetting the session
 * Selenium driver supports Date/Time when filling in date/time/datetime-local inputs
 * `current_url` returns the url for the top level browsing context
@@ -1138,7 +1302,7 @@ Release date: 2016-01-27
 
 # Version 2.6.0
 
-Relase date: 2016-01-17
+Release date: 2016-01-17
 
 ### Fixed
 
@@ -1202,7 +1366,7 @@ Release date: 2014-10-13
 
 # Version 2.4.3
 
-Relase date: 2014-09-21
+Release date: 2014-09-21
 
 ### Fixed
 
@@ -1877,4 +2041,3 @@ too many users, please read the release notes carefully!
 * clicking links where the image's alt attribute contains the text is now possible
 * within_fieldset and within_table work when the default selector is CSS
 * boolean attributes work the same across drivers (return true/false)
-

data/README.md

@@ -1,11 +1,8 @@
 # Capybara
 
-[![Build Status](https://secure.travis-ci.org/teamcapybara/capybara.svg)](https://travis-ci.org/teamcapybara/capybara)
-[![Build Status](https://ci.appveyor.com/api/projects/status/github/teamcapybara/capybara?svg=true)](https://ci.appveyor.com/api/projects/github/teamcapybara/capybara)
+[![Build Status](https://github.com/teamcapybara/capybara/actions/workflows/build.yml/badge.svg)](https://github.com/teamcapybara/capybara/actions/workflows/build.yml)
 [![Code Climate](https://codeclimate.com/github/teamcapybara/capybara.svg)](https://codeclimate.com/github/teamcapybara/capybara)
 [![Coverage Status](https://coveralls.io/repos/github/teamcapybara/capybara/badge.svg?branch=master)](https://coveralls.io/github/teamcapybara/capybara?branch=master)
-[![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/jnicklas/capybara?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
-[![SemVer](https://api.dependabot.com/badges/compatibility_score?dependency-name=capybara&package-manager=bundler&version-scheme=semver)](https://dependabot.com/compatibility-score.html?dependency-name=capybara&package-manager=bundler&version-scheme=semver)
 
 Capybara helps you test web applications by simulating how a real user would
 interact with your app. It is agnostic about the driver running your tests and
@@ -18,8 +15,7 @@ If you and/or your company find value in Capybara and would like to contribute f
 <a href="https://www.patreon.com/capybara">Patreon</a>
 
 
-**Need help?** Ask on the mailing list (please do not open an issue on
-GitHub): http://groups.google.com/group/ruby-capybara
+**Need help?** Ask on the discussions (please do not open an issue): https://github.com/orgs/teamcapybara/discussions/categories/q-a
 
 ## Table of contents
 
@@ -34,7 +30,6 @@ GitHub): http://groups.google.com/group/ruby-capybara
     - [Selecting the Driver](#selecting-the-driver)
     - [RackTest](#racktest)
     - [Selenium](#selenium)
-    - [Apparition](#apparition)
 - [The DSL](#the-dsl)
     - [Navigating](#navigating)
     - [Clicking links and buttons](#clicking-links-and-buttons)
@@ -46,6 +41,10 @@ GitHub): http://groups.google.com/group/ruby-capybara
     - [Scripting](#scripting)
     - [Modals](#modals)
     - [Debugging](#debugging)
+- [Selectors](#selectors)
+    - [Name](#selectors-name)
+    - [Locator](#selectors-locator)
+    - [Filters](#selectors-filters)
 - [Matching](#matching)
     - [Exactness](#exactness)
     - [Strategy](#strategy)
@@ -74,7 +73,7 @@ GitHub): http://groups.google.com/group/ruby-capybara
 
 ## <a name="setup"></a>Setup
 
-Capybara requires Ruby 2.5.0 or later. To install, add this line to your
+Capybara requires Ruby 3.0.0 or later. To install, add this line to your
 `Gemfile` and run `bundle install`:
 
 ```ruby
@@ -145,11 +144,13 @@ Load RSpec 3.5+ support by adding the following line (typically to your
 require 'capybara/rspec'
 ```
 
-If you are using Rails, put your Capybara specs in `spec/features` or `spec/system` (only works
-if [you have it configured in
-RSpec](https://relishapp.com/rspec/rspec-rails/v/4-0/docs/directory-structure))
-and if you have your Capybara specs in a different directory, then tag the
-example groups with `type: :feature` or `type: :system` depending on which type of test you're writing.
+If you are using Rails, put your Capybara specs in `spec/features` or `spec/system` (only works if
+[you have it configured in RSpec](https://rspec.info/features/6-0/rspec-rails/directory-structure/))
+and if you have your Capybara specs in a different directory, then tag the example groups with
+`type: :feature` or `type: :system` depending on which type of test you're writing.
+
+If you are using Rails system specs please see [their documentation](https://rspec.info/features/6-0/rspec-rails/system-specs/system-specs)
+for selecting the driver you wish to use.
 
 If you are not using Rails, tag all the example groups in which you want to use
 Capybara with `type: :feature`.
@@ -159,7 +160,7 @@ You can now write your specs like so:
 ```ruby
 describe "the signin process", type: :feature do
   before :each do
-    User.make(email: 'user@example.com', password: 'password')
+    User.create(email: 'user@example.com', password: 'password')
   end
 
   it "signs me in" do
@@ -181,7 +182,7 @@ to one specific driver. For example:
 ```ruby
 describe 'some stuff which requires js', js: true do
   it 'will use the default js driver'
-  it 'will switch to one specific driver', driver: :apparition
+  it 'will switch to one specific driver', driver: :selenium
 end
 ```
 
@@ -190,7 +191,7 @@ Capybara also comes with a built in DSL for creating descriptive acceptance test
 ```ruby
 feature "Signing in" do
   background do
-    User.make(email: 'user@example.com', password: 'caplin')
+    User.create(email: 'user@example.com', password: 'caplin')
   end
 
   scenario "Signing in with correct credentials" do
@@ -203,7 +204,7 @@ feature "Signing in" do
     expect(page).to have_content 'Success'
   end
 
-  given(:other_user) { User.make(email: 'other@example.com', password: 'rous') }
+  given(:other_user) { User.create(email: 'other@example.com', password: 'rous') }
 
   scenario "Signing in as another user" do
     visit '/sessions/new'
@@ -258,6 +259,8 @@ end
 
 ## <a name="using-capybara-with-minitest"></a>Using Capybara with Minitest
 
+* If you are using Rails system tests please see their documentation for information on selecting the driver you wish to use.
+
 * If you are using Rails, but not using Rails system tests, add the following code in your `test_helper.rb`
     file to make Capybara available in all test cases deriving from
     `ActionDispatch::IntegrationTest`:
@@ -332,7 +335,7 @@ By default, Capybara uses the `:rack_test` driver, which is fast but limited: it
 does not support JavaScript, nor is it able to access HTTP resources outside of
 your Rack application, such as remote APIs and OAuth services. To get around
 these limitations, you can set up a different default driver for your features.
-For example if you'd prefer to run everything in Selenium, you could do:
+For example, if you'd prefer to run everything in Selenium, you could do:
 
 ```ruby
 Capybara.default_driver = :selenium # :selenium_chrome and :selenium_chrome_headless are also registered
@@ -349,7 +352,7 @@ You can also change the driver temporarily (typically in the Before/setup and
 After/teardown blocks):
 
 ```ruby
-Capybara.current_driver = :apparition # temporarily select different driver
+Capybara.current_driver = :selenium # temporarily select different driver
 # tests here
 Capybara.use_default_driver       # switch back to default driver
 ```
@@ -405,15 +408,6 @@ to the browsers.  See the section on adding and configuring drivers.
 same transaction as your tests, causing data not to be shared between your test
 and test server, see [Transactions and database setup](#transactions-and-database-setup) below.
 
-### <a name="apparition"></a>Apparition
-
-The [apparition driver](https://github.com/twalpole/apparition) is a new driver that allows you to run tests using Chrome in a headless
-or headed configuration. It attempts to provide backwards compatibility with the [Poltergeist driver API](https://github.com/teampoltergeist/poltergeist)
-and [capybara-webkit API](https://github.com/thoughtbot/capybara-webkit) while allowing for the use of modern JS/CSS. It
-uses CDP to communicate with Chrome, thereby obviating the need for chromedriver. This driver is being developed by the
-current developer of Capybara and will attempt to keep up to date with new Capybara releases. It will probably be moved into the
-teamcapybara repo once it reaches v1.0.
-
 ## <a name="the-dsl"></a>The DSL
 
 *A complete reference is available at
@@ -626,12 +620,12 @@ JS
 
 ### <a name="modals"></a>Modals
 
-In drivers which support it, you can accept, dismiss and respond to alerts, confirms and prompts.
+In drivers which support it, you can accept, dismiss and respond to alerts, confirms, and prompts.
 
-You can accept or dismiss alert messages by wrapping the code that produces an alert in a block:
+You can accept alert messages by wrapping the code that produces an alert in a block:
 
 ```ruby
-accept_alert do
+accept_alert 'optional text or regex' do
   click_link('Show Alert')
 end
 ```
@@ -639,7 +633,13 @@ end
 You can accept or dismiss a confirmation by wrapping it in a block, as well:
 
 ```ruby
-dismiss_confirm do
+accept_confirm 'optional text' do
+  click_link('Show Confirm')
+end
+```
+
+```ruby
+dismiss_confirm 'optional text' do
   click_link('Show Confirm')
 end
 ```
@@ -647,7 +647,13 @@ end
 You can accept or dismiss prompts as well, and also provide text to fill in for the response:
 
 ```ruby
-accept_prompt(with: 'Linus Torvalds') do
+accept_prompt('optional text', with: 'Linus Torvalds') do
+  click_link('Show Prompt About Linux')
+end
+```
+
+```ruby
+dismiss_prompt('optional text') do
   click_link('Show Prompt About Linux')
 end
 ```
@@ -697,6 +703,148 @@ Screenshots are saved to `Capybara.save_path`, relative to the app directory.
 If you have required `capybara/rails`, `Capybara.save_path` will default to
 `tmp/capybara`.
 
+## <a name="selectors"></a>Selectors
+
+Helpers and matchers that accept Selectors share a common method signature that
+includes:
+
+1. a positional Name argument
+2. a positional Locator argument
+3. keyword Filter arguments
+4. a predicate Filter block argument
+
+These arguments are usually optional in one way or another.
+
+### <a name="selectors-name"></a>Name
+
+The name argument determines the Selector to use. The argument is optional when
+a helper explicitly conveys the selector name (for example, [`find_field`][]
+uses `:field`, [`find_link`][] uses `:link`, etc):
+
+```ruby
+page.html # => '<a href="/">Home</a>'
+
+page.find(:link) == page.find_link
+
+page.html # => '<input>'
+
+page.find(:field) == page.find_field
+```
+
+### <a name="selectors-locator"></a>Locator
+
+The locator argument usually represents information that can most meaningfully
+distinguish an element that matches the selector from an element that does not:
+
+```ruby
+page.html # => '<div id="greeting">Hello world</div>'
+
+page.find(:css, 'div').text     # => 'Hello world'
+page.find(:xpath, './/div').text # => 'Hello world'
+```
+
+General purpose finder methods like [`find`][] and [`all`][] can accept the
+locator as their first positional argument when the method can infer the default
+value from the [`Capybara.default_selector`][] configuration:
+
+```ruby
+page.html # => '<div id="greeting">Hello world</div>'
+
+Capybara.default_selector = :css
+
+page.find('div').text     # => 'Hello world'
+
+Capybara.default_selector = :xpath
+
+page.find('.//div').text # => 'Hello world'
+```
+
+The locator argument's semantics are context-specific, and depend on the
+selector. The types of arguments are varied. Some selectors support `String` or
+`Regexp` arguments, while others like `:table_row` support `Array<String>` and
+`Hash<String, String>`:
+
+```ruby
+page.html # => '<label for="greeting">Greeting</label>
+                <input id="greeting" name="content">'
+
+# find by the <input> element's [id] attribute
+page.find(:id, 'greeting') == page.find_by_id('greeting') # => true
+
+# find by the <input> element's [id] attribute
+page.find(:field, 'greeting') == page.find_field('greeting') # => true
+
+# find by the <input> element's [name] attribute
+page.find(:field, 'content') == page.find_field('content') # => true
+
+# find by the <label> element's text
+page.find(:field, 'Greeting') == page.find_field('Greeting') # => true
+
+page.html # => '<table>
+                  <tr>
+                    <th>A</th>
+                    <th>B</th>
+                  </tr>
+                  <tr>
+                    <td>1</td>
+                    <td>2</td>
+                  </tr>
+                </table>'
+
+# find by <td> content
+page.find(:table_row, ['1', '2']) == page.find(:css, 'tr:last-of-type') # => true
+
+# find by <th> content paired with corresponding <td> content
+page.find(:table_row, 'A' => '1') == page.find(:table_row, 'B' => '2') # => true
+```
+
+### <a name="selectors-filters"></a> Filters
+
+All filters are optional. The supported set of keys is a mixture of both global
+and context-specific filters.The supported types of values depend on the
+context:
+
+```ruby
+page.html # => '<a href="/">Home</a>'
+
+# find by the [href] attribute
+page.find_link(href: '/') == page.find_link(text: 'Home') # => true
+
+page.html # => '<div id="element" data-attribute="value">Content</div>'
+
+# find by the [id] attribute
+page.find(id: 'element') == page.find(text: 'Content') # => true
+
+# find by the [data-attribute] attribute
+page.find(:element, 'data-attribute': /value/) == page.find(text: 'Content') # => true
+
+page.html # => '<input type="checkbox">'
+
+# find by the absence of the [checked] attribute
+page.find_field(checked: false) == page.find_field(unchecked: true) # => true
+```
+
+The predicate block is always optional. When there are results for a selector
+query, the block is called with each item in the result set. When the block
+evaluates to true, the item is included from the result set. Otherwise, the item
+is excluded:
+
+```ruby
+page.html # => '<input role="switch" type="checkbox" checked>'
+
+switch = page.find_field { |input| input["role"] == "switch" }
+field = page.find_field(checked: true)
+
+switch == field # => true
+```
+
+[`find`]: https://rubydoc.info/github/teamcapybara/capybara/master/Capybara/Node/Finders:find
+[`all`]: https://rubydoc.info/github/teamcapybara/capybara/master/Capybara/Node/Finders:all
+[`Capybara.default_selector`]: https://rubydoc.info/github/teamcapybara/capybara/master/Capybara%2Econfigure
+[`find_by_id`]: https://rubydoc.info/github/teamcapybara/capybara/master/Capybara/Node/Finders:find_by_id
+[`find_field`]: https://rubydoc.info/github/teamcapybara/capybara/master/Capybara/Node/Finders:find_field
+[`find_link`]: https://rubydoc.info/github/teamcapybara/capybara/master/Capybara/Node/Finders:find_link
+
 ## <a name="matching"></a>Matching
 
 It is possible to customize how Capybara finds elements. At your disposal
@@ -777,7 +925,7 @@ expect(page).to have_content('baz')
 If clicking on the *foo* link triggers an asynchronous process, such as
 an Ajax request, which, when complete will add the *bar* link to the page,
 clicking on the *bar* link would be expected to fail, since that link doesn't
-exist yet. However Capybara is smart enough to retry finding the link for a
+exist yet. However, Capybara is smart enough to retry finding the link for a
 brief period of time before giving up and throwing an error. The same is true of
 the next line, which looks for the content *baz* on the page; it will retry
 looking for that content for a brief time. You can adjust how long this period
@@ -791,13 +939,25 @@ Be aware that because of this behaviour, the following two statements are **not*
 equivalent, and you should **always** use the latter!
 
 ```ruby
-!page.has_xpath?('a')
-page.has_no_xpath?('a')
+# Given use of a driver where the page is loaded when visit returns
+# and that Capybara.predicates_wait is `true`
+# consider a page where the `a` tag is removed through AJAX after 1s
+visit(some_path)
+!page.has_xpath?('a')  # is false
+page.has_no_xpath?('a')  # is true
 ```
 
-The former would immediately fail because the content has not yet been removed.
-Only the latter would wait for the asynchronous process to remove the content
-from the page.
+First expression:
+- `has_xpath?('a')` is called right after `visit` returns. It is `true` because the link has not yet been removed
+- Capybara does not wait upon successful predicates/assertions, therefore **has_xpath? returns `true` immediately**
+- The expression returns `false` (because it is negated with the leading `!`)
+
+Second expression:
+- `has_no_xpath?('a')` is called right after `visit` returns. It is `false` because the link has not yet been removed.
+- Capybara waits upon failed predicates/assertions, therefore **has_no_xpath? does not return `false` immediately**
+- Capybara will periodically re-check the predicate/assertion up to the `default_max_wait_time` defined
+- after 1s, the predicate becomes `true` (because the link has been removed)
+- The expression returns `true`
 
 Capybara's RSpec matchers, however, are smart enough to handle either form.
 The two following statements are functionally equivalent:

data/lib/capybara/config.rb

@@ -7,10 +7,12 @@ module Capybara
   class Config
     extend Forwardable
 
-    OPTIONS = %i[app reuse_server threadsafe server default_driver javascript_driver allow_gumbo].freeze
+    OPTIONS = %i[
+      app reuse_server threadsafe server default_driver javascript_driver use_html5_parsing allow_gumbo
+    ].freeze
 
-    attr_accessor :app, :allow_gumbo
-    attr_reader :reuse_server, :threadsafe, :session_options
+    attr_accessor :app, :use_html5_parsing
+    attr_reader :reuse_server, :threadsafe, :session_options # rubocop:disable Style/BisectedAttrAccessor
     attr_writer :default_driver, :javascript_driver
 
     SessionConfig::OPTIONS.each do |method|
@@ -22,7 +24,7 @@ module Capybara
       @javascript_driver = nil
     end
 
-    attr_writer :reuse_server
+    attr_writer :reuse_server # rubocop:disable Style/BisectedAttrAccessor
 
     def threadsafe=(bool)
       if (bool != threadsafe) && Session.instance_created?
@@ -88,5 +90,15 @@ module Capybara
       end
       @deprecation_notified[method] = true
     end
+
+    def allow_gumbo=(val)
+      deprecate('allow_gumbo=', 'use_html5_parsing=')
+      self.use_html5_parsing = val
+    end
+
+    def allow_gumbo
+      deprecate('allow_gumbo', 'use_html5_parsing')
+      use_html5_parsing
+    end
   end
 end

data/lib/capybara/driver/base.rb

@@ -63,6 +63,10 @@ class Capybara::Driver::Base
     raise Capybara::NotSupportedByDriverError, 'Capybara::Driver::Base#send_keys'
   end
 
+  def active_element
+    raise Capybara::NotSupportedByDriverError, 'Capybara::Driver::Base#active_element'
+  end
+
   ##
   #
   # @param frame [Capybara::Node::Element, :parent, :top]  The iframe element to switch to

data/lib/capybara/driver/node.rb

@@ -125,6 +125,10 @@ module Capybara
         raise NotSupportedByDriverError, 'Capybara::Driver::Node#trigger'
       end
 
+      def shadow_root
+        raise NotSupportedByDriverError, 'Capybara::Driver::Node#shadow_root'
+      end
+
       def inspect
         %(#<#{self.class} tag="#{tag_name}" path="#{path}">)
       rescue NotSupportedByDriverError
@@ -132,7 +136,7 @@ module Capybara
       end
 
       def ==(other)
-        raise NotSupportedByDriverError, 'Capybara::Driver::Node#=='
+        eql?(other) || (other.respond_to?(:native) && native == other.native)
       end
     end
   end