htmx: Failed upgrade makes hx-boost clicks silent – is the default changed?

Question

Problem Statement
After upgrading the htmx library, click interactions that previously relied on hx-boost no longer trigger requests. The page loads, but the console shows no network activity and the DOM does not update.
Diagnostic Constraints
• The application pins a specific htmx file via a CDN, using SRI where possible.
• A prior build remains deployable; rollback is a static‑file change.
• Extensions may have been updated concurrently; the new core may have altered default delegation rules.
• Browser caches can mask which asset is actually executed.
Unresolved Decision
We must determine whether the symptom stems from a changed hx-boost default, an incompatible extension, or a caching artifact before deciding to roll back or refactor markup.
Questions for Investigation

Did the htmx release that replaced the previous version modify the default event delegation behavior of hx-boost?
Are there any renamed, removed, or added attributes required for hx-boost to function in the new version?
Which version‑specific documentation sections detail changes to hx-boost or its interaction with extensions?

Tasadduq Burney · Answer

The Short Answer

Yes, the default behavior changed. In htmx 2.0, the automatic "global" boosting of all anchor and form elements was removed. hx-boost now operates on an opt-in basis, meaning the attribute must be explicitly present on the element (or a parent element) to trigger an AJAX request.

Likely Explanation vs. Confirmed Behavior

Confirmed Behavior: According to the htmx 2.0 migration specifications, the library no longer uses global document click delegation to automatically boost every link and form. The hx-boost attribute remains the correct mechanism, but it is no longer applied by default to the entire page unless specified.

Likely Explanation for "Silent" Clicks: If your previous version relied on this global behavior, your elements are now behaving as standard HTML links/forms. Because they lack the explicit hx-boost attribute, htmx ignores them entirely, resulting in no network activity in the console and no DOM updates, as the browser is not being instructed to intercept the event.

Verification and Resolution Steps

To resolve this and rule out caching or extension conflicts, perform these scoped checks:

Verify Active Version: Open the browser Developer Tools Network tab. Locate the htmx script request and verify the version string. If the version is 2.0.0 or higher, the change in default behavior is the cause.
Test Explicit Opt-in: Manually add the hx-boost attribute to a single failing element:
```
<a href="/example" hx-boost>Test Link</a>
```
If the request now appears in the Network tab, the issue is the missing attribute.
Rule Out Cache/SRI: Perform a hard reload (Ctrl+F5 or Cmd+Shift+R). If the behavior changes, a cached version of an older script or an SRI mismatch may have been causing inconsistent execution.
Isolate Extensions: If the attribute is present but clicks remain silent, temporarily remove any htmx extensions. Some extensions designed for 1.x may interfere with the new event delegation model in 2.0.

Required Diagnostic Detail

To provide a more specific recommendation regarding extensions, please specify which htmx extensions (if any) were updated concurrently with the core library.

htmx: Failed upgrade makes hx-boost clicks silent – is the default changed?

Problem Statement

Diagnostic Constraints

Unresolved Decision

Questions for Investigation

1 answer

The Short Answer

Likely Explanation vs. Confirmed Behavior

Verification and Resolution Steps

Required Diagnostic Detail

Your perspective belongs here.

0 question comments