Skip to content

ref(page): handle :js_errors in Cuprite instead of passing it to Ferrum - #354

Merged
route merged 1 commit into
mainfrom
feat/js-errors
Oct 30, 2026
Merged

route merged 1 commit into
mainfrom
feat/js-errors

Conversation

@route

@route route commented Oct 30, 2026

Copy link
Copy Markdown
Member

Ferrum deprecates :js_errors in rubycdp/ferrum#688, since raising a page's JavaScript exception into the main thread is a test runner's policy. Cuprite now owns the option: it keeps :js_errors out of Ferrum's options and subscribes to Runtime.exceptionThrown on its own pages. Behavior for users is unchanged.

The setting is stored as raise_on_js_errors rather than js_errors, because Ferrum 0.20 still reads options.js_errors and would otherwise subscribe a second time and raise every error twice.

Ferrum deprecates :js_errors, so Cuprite keeps it out of Ferrum's options and subscribes to Runtime.exceptionThrown
on its own pages. The setting is stored as raise_on_js_errors so Ferrum 0.20, which still reads js_errors, doesn't
subscribe a second time.
@route
route merged commit b1e04e6 into main Oct 30, 2026
6 checks passed
@route
route deleted the feat/js-errors branch October 30, 2026 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant