Tim Fischbach

This also happens when a style is composed in multiple places: _utils.css_ ``` .someUtil { color: blue; } ``` _a.css_ ``` .styleA { composes: someUtil from './utils.css'; color: green; }...

Very much in favor of this change. Ran into issues several times where files from old cookbook versions were still around and caused the chef run to fail. Not much...

Can confirm the issue. Also have it working with chef 11.4. No problems so far.

Relevant to make it work with Chrome 120: https://github.com/SeleniumHQ/selenium/issues/13112. TLDR: use `--headless=new` instead of `--headless`.

Just wanted to note that, starting with Zeitwerk, [`Engine#eager_load!` is no-op](https://github.com/rails/rails/blob/0b2fb5d29f1c67762fb62ab42436a36526e4f1d9/railties/lib/rails/engine.rb#L484) now.

Rebased onto main. Updated jsbin showcasing the new behavior using the latest version of Video.js: https://jsbin.com/vipikadeni/edit?html,output

Well yeah, but sometimes you already are on the correct page but still have to wait for stuff to appear (i.e. ajax).

This also seems to be the way capybara [implements waiting](https://github.com/jnicklas/capybara/blob/ba5ba340e8847105312de16705a80dfb5ee92475/lib/capybara/node/base.rb#L76). Still, it somehow feels like re-implementing capybara features in domino.

The error is still the same in Rails 7.1.3. Can this issue be re-opened or should I create an identical one for the new Rails version?

The above steps still reproduce the problem for me. Full stack trace of the final command ``` $ bin/rails db:create:all --trace ** Invoke db:create:all (first_time) ** Invoke db:load_config (first_time) **...