capybara-dommy 0.10.0 → 0.12.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ce693099e9f737e726914acb5cf9129ad87a96978209f5b1d9cc27132925b652
-  data.tar.gz: a69e70e2f0878025fd8d8c5a9411aaa990d6ebd7f812bd623cd3f27c4614e3bd
+  metadata.gz: '09b82196b4134a59d541a83732013edf23a017a47776dd35b326ebc573747789'
+  data.tar.gz: 282eb35b9f51404a80602537ad3fe6f29a7af768da2b30210c483fc8a841f86b
 SHA512:
-  metadata.gz: 1f351cf3f7989d3bfa1a984dc425cf895790350ed699431f1e6fb8a7d6708c8b1abc05ab20df20f129839a0c926074d6b64774b9885a97b593ad41b8354b0b2a
-  data.tar.gz: 4246e91a681b995f8cc2fb2633eac92a1d6e5b1fc8dad67954d099124cc999055575597a59a94965ea6d37b201ed04d9ec2271a6dbd0146d7eede6b634a416cc
+  metadata.gz: 6f9e7b3ca7e5bb3bde8c5c465bbdf783ba7497c4a40f032927fb6d34a1416c53cb73e321ee5902e1a9c215028e0b1e7665dbe7dc3ad92842a64fa001a3844d0a
+  data.tar.gz: 9aed884b51865fd48c233f9d7c4c8b63b50798f1cf18850701048d42671c8b0e5c071657850db0e49f9487b2b519b50ab8b74ae3f58cc58913646f53b6171cee

data/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 0.12.0 — 2026-09-22
+
+Versioned in lockstep with [`dommy`](https://github.com/takahashim/dommy) 0.12.0.
+No functional changes to capybara-dommy itself.
+
+## 0.11.0 — 2026-09-11
+
+### Added
+- **Native dialog helpers in JS mode.** `accept_confirm`, `dismiss_confirm`, `accept_alert`, `accept_prompt` (with `with:`) and `dismiss_prompt` work against the page's real `confirm` / `alert` / `prompt`, including a `text:` string or Regexp to say which dialog is expected. Nested helper blocks answer the dialogs in the order the page opens them, and a dialog nobody is waiting for falls back to the headless default, so a stray `confirm` cannot silently accept. A block that opens no matching dialog raises `Capybara::ModalNotFound`, naming what turned up instead.
+
+### Fixed
+- Turbo-driven navigation in JS apps is followed, so `have_current_path` and the matchers after a Turbo visit see the page the app actually moved to.
+- `current_url` advances the virtual clock like the other queries do, so a `have_current_path` poll converges when the navigation settles in a scheduled task rather than a microtask.
+
 ## 0.10.0 — 2026-07-13
 
 ### Added

data/README.md

@@ -19,15 +19,24 @@ speed and simplicity of a Rack-style driver.
 - Preserves session state such as cookies, follows redirects by default, and
   supports browser-like back, forward, and refresh navigation.
 - Implements HTML-level visibility through `dommy-rack`.
+- In JavaScript-enabled mode, supports Capybara's `accept_alert`,
+  `accept_confirm`, `dismiss_confirm`, `accept_prompt`, and `dismiss_prompt`
+  helpers with deterministic responses.
 - Provides a Rails convenience require for `driven_by :dommy`.
 
 ## Limitations
 
 `capybara-dommy` is intentionally not a browser automation driver.
 
-- JavaScript is not executed.
-- Screenshots, browser windows, alerts, confirms, prompts, and other real
-  browser features are not supported.
+- The default driver does not execute JavaScript. Use the JavaScript-enabled
+  variant for embedded QuickJS execution.
+- Screenshots and browser windows are not supported. Native alerts, confirms,
+  and prompts are supported by the JavaScript-enabled variant through
+  Capybara's modal helpers.
+- Constructable stylesheets can be built (`new CSSStyleSheet()`), but
+  `adoptedStyleSheets` is not implemented — assigning one applies no style.
+  Component libraries that feature-detect (`'adoptedStyleSheets' in
+  Document.prototype`) fall back to injecting a `<style>`, which is handled.
 - CSS layout is not calculated. Visibility is based on HTML-level rules such as
   `hidden`, `type="hidden"`, and inline `display: none` handling provided by
   `dommy-rack`.

data/lib/capybara/dommy/driver.rb

@@ -4,9 +4,10 @@ module Capybara
   module Dommy
     # A Capybara driver backed by Dommy::Rack::Session. Implements the
     # navigation / query / reset! parts of the Capybara::Driver::Base contract;
-    # element interaction lives in Capybara::Dommy::Node. JavaScript, screenshot,
-    # window, and modal methods are left to Driver::Base (which raises
-    # Capybara::NotSupportedByDriverError).
+    # element interaction lives in Capybara::Dommy::Node. The JS-enabled mode
+    # additionally supplies deterministic native dialog responses for Capybara's
+    # alert/confirm/prompt helpers. Screenshot and window methods remain with
+    # Driver::Base (which raises Capybara::NotSupportedByDriverError).
     class Driver < Capybara::Driver::Base
       VISIBILITY_MODES = %i[all html none].freeze
 
@@ -94,6 +95,12 @@ module Capybara
       end
 
       def current_url
+        # Capybara polls current_url for have_current_path. In JS mode that poll
+        # must advance the virtual clock too: Turbo/fetch continuations often
+        # settle in a scheduled task rather than the interaction's microtask
+        # drain. The Rack session's History hook then reflects pushState in its
+        # current URL.
+        pump!
         rack_session.current_url.to_s
       end
 
@@ -240,6 +247,22 @@ module Capybara
         unsupported_js!("evaluate_async_script")
       end
 
+      # --- Native dialogs ---
+      #
+      # A native dialog is synchronous in Dommy, so installing the expected
+      # answer before the triggering block runs is sufficient. What is expected,
+      # what it answers and what it saw instead live in ModalExpectation; the
+      # stack they sit on, which is the session's dialog handler while a helper
+      # block is running, is ModalStack.
+
+      def accept_modal(type, **options, &block)
+        respond_to_modal(type, accept: true, **options, &block)
+      end
+
+      def dismiss_modal(type, **options, &block)
+        respond_to_modal(type, accept: false, **options, &block)
+      end
+
       # Visibility decision used by Node#visible?. :all / :none treat every
       # element as visible; :html defers to dommy-rack's HTML-level check.
       def visible?(element)
@@ -323,6 +346,26 @@ module Capybara
         raise Capybara::NotSupportedByDriverError,
               "capybara-dommy does not support JavaScript (#{name})"
       end
+
+      def respond_to_modal(type, accept:, text: nil, with: nil, **_options)
+        expectation = ModalExpectation.new(type: type, accept: accept, text: text, with: with)
+        modals.push(expectation)
+        rack_session.dialog_handler = modals
+        yield if block_given?
+
+        raise Capybara::ModalNotFound, expectation.not_found_message unless expectation.answered?
+
+        expectation.message
+      ensure
+        if expectation
+          modals.delete(expectation)
+          rack_session.dialog_handler = nil if modals.empty? && @rack_session
+        end
+      end
+
+      def modals
+        @modals ||= ModalStack.new
+      end
     end
   end
 end

data/lib/capybara/dommy/modal.rb

@@ -0,0 +1,114 @@
+# frozen_string_literal: true
+
+module Capybara
+  module Dommy
+    # What one `accept_modal` / `dismiss_modal` block is waiting for, and what
+    # it saw. A native dialog is synchronous in Dommy, so the expectation is
+    # installed before the triggering block runs and answers the dialog the
+    # block opens.
+    class ModalExpectation
+      attr_reader :type, :text
+      # The message of the dialog this expectation answered — nil while it is
+      # still waiting, which is what makes it "not found" at the end of the
+      # block.
+      attr_reader :message
+
+      def initialize(type:, accept:, text: nil, with: nil)
+        @type = type.to_sym
+        @accept = accept
+        @text = text
+        @with = with
+        @message = nil
+        @actual = nil
+      end
+
+      def matches?(type, message)
+        @type == type && text_matches?(message)
+      end
+
+      def answered? = !@message.nil?
+
+      # Record that this dialog is the one, and answer it: a confirm with the
+      # accept/dismiss decision, a prompt with the text to type (`with:`, else
+      # what the page offered) or nil when dismissed. An alert has no answer.
+      def answer(message, default_value)
+        @message = message
+        case @type
+        when :confirm then @accept
+        when :prompt then @accept ? (@with || default_value) : nil
+        end
+      end
+
+      # A dialog this expectation did not want. Remembered for the error at the
+      # end of the block, which says what turned up instead.
+      def saw(type, message)
+        @actual = {type: type, message: message}
+        nil
+      end
+
+      def not_found_message
+        if @actual
+          "Unable to find #{@type} dialog with #{@text.inspect} - found " \
+            "#{@actual[:type]} dialog with #{@actual[:message].inspect} instead."
+        else
+          "Unable to find #{@type} dialog#{@text ? " with #{@text.inspect}" : ""}"
+        end
+      end
+
+      private
+
+      def text_matches?(message)
+        return true if @text.nil?
+
+        pattern = @text.is_a?(Regexp) ? @text : Regexp.new(Regexp.escape(@text.to_s))
+        pattern.match?(message)
+      end
+    end
+
+    # The expectations currently in scope, innermost first, as the dialog
+    # handler a Dommy Window asks (it calls `#call`).
+    #
+    # A stack, because Capybara expresses nested confirms as nested helper
+    # blocks while the page opens them sequentially in one JS call stack:
+    # consuming the inner expectation exposes the outer answer to the next
+    # confirm immediately.
+    class ModalStack
+      def initialize
+        @expectations = []
+      end
+
+      def empty? = @expectations.empty?
+
+      def push(expectation)
+        @expectations << expectation
+        expectation
+      end
+
+      # By identity: two helper blocks with the same arguments build EQUAL
+      # expectations, and removing by value would drop the caller's alongside
+      # this one.
+      def delete(expectation)
+        @expectations.delete_if { |e| e.equal?(expectation) }
+        nil
+      end
+
+      # The dialog handler protocol: answer the dialog, or return
+      # DIALOG_UNANSWERED to leave it to the Window's headless default. An
+      # expectation that does not want this dialog remembers it (so the block
+      # can say what turned up instead) and declines rather than answering.
+      def call(type, message, default_value)
+        expectation = @expectations.last
+        return ::Dommy::Window::DIALOG_UNANSWERED if expectation.nil?
+
+        unless expectation.matches?(type, message)
+          expectation.saw(type, message)
+          return ::Dommy::Window::DIALOG_UNANSWERED
+        end
+
+        answer = expectation.answer(message, default_value)
+        delete(expectation)
+        answer
+      end
+    end
+  end
+end

data/lib/capybara/dommy/version.rb

@@ -2,6 +2,6 @@
 
 module Capybara
   module Dommy
-    VERSION = "0.10.0"
+    VERSION = "0.12.0"
   end
 end

data/lib/capybara/dommy.rb

@@ -8,6 +8,7 @@ require_relative "dommy/version"
 require_relative "dommy/errors"
 require_relative "dommy/configuration"
 require_relative "dommy/text_extractor"
+require_relative "dommy/modal"
 require_relative "dommy/node"
 require_relative "dommy/driver"
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: capybara-dommy
 version: !ruby/object:Gem::Version
-  version: 0.10.0
+  version: 0.12.0
 platform: ruby
 authors:
 - takahashim
@@ -29,28 +29,28 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.10.0
+        version: 0.12.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.10.0
+        version: 0.12.0
 - !ruby/object:Gem::Dependency
   name: dommy-rack
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.10.0
+        version: 0.12.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.10.0
+        version: 0.12.0
 description: |
   capybara-dommy is a Capybara driver backed by Dommy and dommy-rack. It drives
   Rack/Rails apps through the Capybara DSL without a real browser or JavaScript,
@@ -69,6 +69,7 @@ files:
 - lib/capybara/dommy/configuration.rb
 - lib/capybara/dommy/driver.rb
 - lib/capybara/dommy/errors.rb
+- lib/capybara/dommy/modal.rb
 - lib/capybara/dommy/node.rb
 - lib/capybara/dommy/rails.rb
 - lib/capybara/dommy/text_extractor.rb
@@ -94,7 +95,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.10
+rubygems_version: 3.6.9
 specification_version: 4
 summary: A Dommy-backed Capybara driver
 test_files: []