[Greg-Myers-SB]

The alias for these already exist within this file but the options hash did not allow the aliased keys, until now.

Same as 575ef9c extended to options.

[Greg-Myers-SB]

The test failures on 3.1 look the same as these test failures on another branch.
There may be a source of flakiness in the suite.
https://github.com/rubycdp/cuprite/actions/runs/36502102471/job/109195094304

[route]

Thanks for the PR! The idea is good, but as it stands the new keys only work until the first Capybara reset.

Driver#reset! sets both lists again using only the legacy keys:

# lib/capybara/cuprite/driver.rb
browser.url_blacklist = @options[:url_blacklist]
browser.url_whitelist = @options[:url_whitelist]

So when the driver is registered with url_blocklist: / url_allowlist:, @options[:url_blacklist] is nil, prepare_wildcards(nil) returns [], and the list is cleared after the first test. Every test after that runs with no blocklist/allowlist.

To land this, it would need:

• the new keys handled in one place, so Browser#initialize and Driver#reset! agree (for example, by mapping them to the legacy keys once in Driver#initialize)
• a spec like the existing url_blacklist: / url_whitelist: driver-registration specs in spec/features/driver_spec.rb, using the new keys and covering a reset
• a README update for the options list, plus a short CHANGELOG entry

I'm closing this for now. Feel free to reopen or open a new PR with those changes. The 3.1 failure is an unrelated flaky spec, as you noted.

[Greg-Myers-SB]

Hi @route , thank you for the feedback, I have two PRs. #361 addresses your feedback to allow it to survive reset by pushing the change upwards into driver.rb, and Greg-Myers-SB#1 reverses some of the internals so blocklist/allowlist is the preferred terms instead of mapping onto old terms.

I hope these satisfy 🙇

[route]

Looking good, thx!