Bump cuprite from 0.17 to 0.18

[dependabot]

Bumps cuprite from 0.17 to 0.18.

Release notes

Sourced from cuprite's releases.

0.18

Added

• Support time inputs #245
• Add initial support for shadow_root #234
• Support Capybara::Cuprite::Node#rect #276
• Extend Node#set with the datetime-local input type #295
• Support HTML5 drag-and-drop and drag modifier keys in Node#drag_to #315
• Support Element#drop for files and strings #316
• Add :raise_on_unhandled_modal browser option to raise instead of warn on an unhandled modal #320

Changed

• Bump Ferrum dependency to ~> 0.18.0

Fixed

• Ensure the node has focus before setting value #280
• Raise ObsoleteNode instead of silently acting on a node that got disconnected from the DOM between being found and being used #239
• Capybara::Cuprite::Node#send_keys ignores empty or nil keys instead of raising, matching the Selenium and rack_test drivers #313
• Driver#switch_to_frame accepts a Capybara::Cuprite::Node instead of only a wrapped Capybara::Node::Element #312
• Report tag_name as "ShadowRoot" for shadow root nodes #318
• Treat non-summary descendants of a closed <details> element as non-visible #317
• switch_to_window sends Target.activateTarget so Chrome reactivates the window's renderer immediately instead of leaving it backgrounded, which could stall the next input command for several seconds #321
• Node#set fires input and change events for a color input, since its value can only be set via JavaScript and never gets them naturally #229
• Generate a FocusEvent (not a generic Event) for focus-related events (blur, focus, focusin, focusout), matching real browser behavior #272

Changelog

Sourced from cuprite's changelog.

0.18

Added

• Support time inputs #245
• Add initial support for shadow_root #234
• Support Capybara::Cuprite::Node#rect #276
• Extend Node#set with the datetime-local input type #295
• Support HTML5 drag-and-drop and drag modifier keys in Node#drag_to #315
• Support Element#drop for files and strings #316
• Add :raise_on_unhandled_modal browser option to raise instead of warn on an unhandled modal #320

Changed

• Bump Ferrum dependency to ~> 0.18.0

Fixed

• Ensure the node has focus before setting value #280
• Raise ObsoleteNode instead of silently acting on a node that got disconnected from the DOM between being found and being used #239
• Capybara::Cuprite::Node#send_keys ignores empty or nil keys instead of raising, matching the Selenium and rack_test drivers #313
• Driver#switch_to_frame accepts a Capybara::Cuprite::Node instead of only a wrapped Capybara::Node::Element #312
• Report tag_name as "ShadowRoot" for shadow root nodes #318
• Treat non-summary descendants of a closed <details> element as non-visible #317
• switch_to_window sends Target.activateTarget so Chrome reactivates the window's renderer immediately instead of leaving it backgrounded, which could stall the next input command for several seconds #321
• Node#set fires input and change events for a color input, since its value can only be set via JavaScript and never gets them naturally #229
• Generate a FocusEvent (not a generic Event) for focus-related events (blur, focus, focusin, focusout), matching real browser behavior #272

Removed

Commits

• ffdc57d bump up
• 8677fe1 chore: update CHANGELOG.md with updated repository links
• bfddb1f Introduce raise_on_unhandled_modal browser configuration (#324)
• 171c42c Generate a FocusEvent (not Event) for focus-related events (#272)
• 050cb4f chore: add missing changelog entries
• 41dbd80 Fire input and change event on set for color input (#230)
• bf5d1c5 fix: lint
• 8bc6442 fix: ensure switch_to_window activates the target to avoid delays in input ...
• a1e9fc9 Document Ferrum's Docker container mode (#323)
• df27e61 chore: move spec as it's skipped in selenium capybara as well
• Additional commits viewable in compare view

[github-actions]

🎉 A review copy of this PR has been deployed! You can reach it at: https://pr-3119.admin.review.forms.service.gov.uk/

It may take 5 minutes or so for the application to be fully deployed and working. If it still isn't ready
after 5 minutes, there may be something wrong with the ECS task. You will need to go to the integration AWS account
to debug, or otherwise ask an infrastructure person.

For the sign in details and more information, see the review apps wiki page.