Update capybara: 3.16.1 → 3.24.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ capybara (3.16.1 → 3.24.0) · Repo · Changelog

Release Notes

3.24.0 (from changelog)

Release date: 2019-06-13

Added

• Log access when using the Selenium driver with Chrome 75 in W3C mode has been reenabled.

Changed

• Selenium driver now selects all current content and then sends keys rather than clearing field by JS and then sending keys when setting values to text inputs in order to more closely simulate user behavior

Fixed

• Relative paths passed to attach_file will be assumed to be relative to the current working directory when using the Selenium driver

3.23.0 (from changelog)

Release date: 2019-06-10

Added

• Improved error message when using Chrome in W3C mode and attempting to access logs
• Support driver specific options for Element#drag_to
• Support setting <input type="color"> elements with the selenium driver

Fixed

• Tightened conditions when in expression text option matching will be used
• Improved Selenium drivers HTML5 drag and drop emulation compatibility with SortableJS library (and others)

3.22.0 (from changelog)

Release date: 2019-05-29

Added

• ancestor/sibling assertions and matchers added
• Documentation Updates and Fixes - Many thanks again to Masafumi Koba! [Masafumi Koba]
• Added :with alias for :option filter on :checkbox and :radio_button selectors

Changed

• Selenium driver with Chrome >= 73 now resets cookies and local/session storage after navigating to 'about:blank' when possible to minimize potential race condition

3.21.0 (from changelog)

Release date: 2019-05-24

Added

• Element#drop - Chrome and Firefox, via the selenium driver, support dropping files/data on elements
• Default CSS used for attach_file make_visible: true now includes auto for height and width to handle more ways of hiding the file input element
• Documentation Updates and Fixes - Many thanks to Masafumi Koba! [Masafumi Koba]

Changed

• Deprecate support for CSS locator being a Symbol

3.20.2 (from changelog)

Release date: 2019-05-19

Fixed

• Move uglifier from runtime to development dependency [miyucy]

3.20.1 (from changelog)

Release date: 2019-05-17

Fixed

• RackTest driver considers <template> elements to be non-visible and ignores the contents

3.20.0 (from changelog)

Release date: 2019-05-14

Added

• Node#obscured? to check viewport presence and element overlap
• :obscured system filter to check whether elements are obscured in finders, assertions, and expectations
• :label selector :for option can be a regexp
• Significantly smaller isDisplayed/getAttribute atoms for selenium driver. If these produce issues you can disable their use by setting an environment variable named 'DISABLE_CAPYBARA_SELENIUM_OPTIMIZATIONS' (Please also report any issues).
• href: false option with find_link/click_link/:link selector ignores href presence/absence

Fixed

• Workaround Safari issue with send_keys not correctly using top level modifiers
• Workaround Safari not retrying click due to incorrect error type
• Fix Safari attach_file block mode when clicking elements associated to the file input
• Workaround Safari issue with repeated hover

3.19.1 (from changelog)

Release date: 2019-05-11

Fixed

• Fix access to specializations when Selenium::Driver is subclassed [James Mead]

3.19.0 (from changelog)

Release date: 2019-05-09

Added

• Syntactic sugar #once, #twice, #thrice, #exactly, #at_least, #at_most, and #times added to have_selector, have_css, have_xpath, and have_text RSpec matchers
• Support for multiple expression types in Selector definitions
• Reduced wirecalls for common actions in Selenium driver

Fixed

• Workaround Chrome 75 appending files to multiple file inputs
• Suppressed retry when detecting http vs https server connection

3.18.0 (from changelog)

Release date: 2019-04-22

Added

• XPath Selector query optimized to make use of Regexp :text option in initial element find

Fixed

• Workaround issue where Chrome/chromedriver 74 can return the wrong error type when a click is intercepted

Not all release notes shown. View the full release notes

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ nokogiri (indirect, 1.10.2 → 1.10.3) · Repo · Changelog

Release Notes

1.10.3

1.10.3 / 2019-04-22

Security Notes

[MRI] Pulled in upstream patch from libxslt that addresses CVE-2019-11068. Full details are available in #1892. Note that this patch is not yet (as of 2019-04-22) in an upstream release of libxslt.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 5 commits:

• version bump to v1.10.3
• Merge pull request #1898 from sparklemotion/1892-libxslt-patch-for-usn-3947
• Backport libxslt patch for CVE-2019-11068
• Merge branch 'concourse-icons'
• ci: add icons to concourse resources

↗️ public_suffix (indirect, 3.0.3 → 3.1.0) · Repo · Changelog

Release Notes

3.1.0 (from changelog)

• CHANGED: Updated definitions.
• CHANGED: Minimum Ruby version is 2.3
• CHANGED: Upgraded to Bundler 2.x

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 11 commits:

• Release 3.1.0
• Update definitions list (#160)
• Upgrade to Rubocop 0.70
• Fix version mismatch
• Minimum Ruby version is 2.3
• Upgrade Bundler
• Make Travis happy
• Fix typo in comment (#159)
• Fix offenses
• Switch to CodeCov
• Update .travis.yml

↗️ rack (indirect, 2.0.6 → 2.0.7) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 4 commits:

• Bumping to 2.0.7 for release
• Merge pull request #1343 from larsxschneider/ls/forward-fix
• Preserve forwarded IP address for trusted proxy chains
• Merge pull request #1201 from janko-m/make-multipart-parsing-work-for-chunked-requests

↗️ regexp_parser (indirect, 1.3.0 → 1.5.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 32 commits:

• Release v1.5.1
• Deprecate another legacy method
• Standardize parser specs, fix discovered option bug
• Standardize syntax specs
• Standardize scanner and lexer specs
• Standardize lexer specs
• Scanner cleanup - remove deducible ivars
• Standardize scanner specs; fix discovered ts/te bug for `-]`
• Remove more unreachable code, fix \M, \C edge cases
• Fix scan of empty backref/refcall raising ArgumentError
• Simplify options scanning, fix some edge cases
• Improve coverage
• Remove unreachable code
• Extract option shortcuts to own file
• Fix #match and #=~ not working with 1 arg
• Fix #options for some expression classes
• Release v1.5.0
• Update README
• Fix quantification of codepoint lists
• Remove some obsolete ruby version checks
• Fix #initialize_clone direction
• Add #repetitions, #match_length
• Fix Sequence#clone by removing #text -> #to_s circle
• Add #referenced_expression
• Merge pull request #60 from ammar/migrate_to_rspec
• Migrate to RSpec
• Release v1.4.0
• Travis: try using provided bundler
• Add latest unicode properties
• Test against Ruby 2.6
• Merge pull request #58 from amatsuda/https
• GitHub is https by default

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #59.