Tailwind scaffolding generates tests that will fail

[rubys]

Reproduction instructions:

rails new blog --css tailwind
cd blog
bin/rails generate scaffold Post title:string body:text
bin/rails db:migrate
bin/rails test:system

Results:

Results if --css tailwind is omitted:

Running 4 tests in a single process (parallelization threshold is 50)
Run options: --seed 22878

# Running:

Capybara starting Puma...
* Version 6.6.0, codename: Return to Forever
* Min threads: 0, max threads: 4
* Listening on http://127.0.0.1:50646
....

Finished in 1.903383s, 2.1015 runs/s, 2.1015 assertions/s.
4 runs, 4 assertions, 0 failures, 0 errors, 0 skips

[patriciomacadden]

we added back a confirm prompt in #498 .

System tests are created by a generator in rails, not here. Which is why it doesn't consider having a turbo confirm.

The original PR conditionally added the turbo-confirm data attribute if turbo was set up in your project, but that wouldn't solve the issue as the system tests are generated by rails and rails doesn't consider turbo confirm prompts.

I'll give it a go and see if we can add that to the test somehow.

[flavorjones]

Fix shipped in https://github.com/rails/tailwindcss-rails/releases/tag/v4.2.1

[rubys]

Thanks! For context, Agile Web Development with Rails 8 uses tailwind, and I didn't want to have to explain why the tests fail 😃