In certain situations, using an action option such as :prevent can change the order in which actions registered in the same data-action are executed.
Here is a self-contained example demonstrating the problem:
<html>
<head>
<script type="module">
import { Application, Controller } from "https://unpkg.com/@hotwired/stimulus/dist/stimulus.js"
window.Stimulus = Application.start()
Stimulus.debug = true
Stimulus.register("one", class extends Controller {
foo() {}
})
Stimulus.register("two", class extends Controller {
bar() {}
})
</script>
</head>
<body>
<div data-controller="two">
<div data-controller="one">
<a href="#" data-action="one#foo two#bar">Click me</a>
</div>
</div>
</body>
</html>Without the action option, the debug output shows the correct order:
However, if I use an action option:
<a href="#" data-action="one#foo:prevent two#bar">Click me</a>
The debug output shows the order in which actions are executed has changed:
This seems like a bug to me. I encountered it in a scenario where the order of actions was important, and it took me a while to realize it's because of the action option.
In certain situations, using an action option such as
:preventcan change the order in which actions registered in the samedata-actionare executed.Here is a self-contained example demonstrating the problem:
Without the action option, the debug output shows the correct order:
However, if I use an action option:
The debug output shows the order in which actions are executed has changed:
This seems like a bug to me. I encountered it in a scenario where the order of actions was important, and it took me a while to realize it's because of the action option.