Advanced Comment Threads Reaches Beta2 With Teaser, Loading and Cache Improvements

Built for threaded Drupal discussions, Advanced Comment Threads has reached 1.0.0-beta2 with changes to teaser presentation, loading behaviour and cache handling. The 2 October release follows the first beta by one day and continues work on progressive loading, inline replies, unread navigation, filtering, reader preferences and optional live refresh.

The most visible beta2 change is a revised teaser density that clips comment content to four lines by default. Themes can override the line count through the --act-teaser-lines CSS variable, while full-density and focused content remain unclipped. The release also changes the bottom Show all comments link so JavaScript-enabled pages expand and load the discussion in place while retaining the URL fallback when JavaScript is unavailable.

Beta2 continues work on performance under repeated or concurrent requests. Caret prefetching is limited to four visible children and two grandchildren, fragment throttling can pause speculative loading, and polling and prefetch requests respect Retry-After. Diagnostic locking is now scoped by client instead of using one global lock and flood bucket, while per-IP limits remain in place.

The release also enlarges undersized subject and permalink targets, improves narrow-screen permalink focus, and unifies several loading, border, selected-state and focus tokens. Browser tests were updated for the new in-page Show all behaviour, and a timing race in the Expand All loading-state test was removed.

Beta1 Established the Current Architecture

The move to beta began with 1.0.0-beta1 on 1 October. That release introduced shared, access-aware thread snapshots for refresh requests, with per-host invalidation, rebuild locking, a short stale fallback and a configurable cache switch. It also added a Show all text toggle, allowed concurrent fragment requests from one client and added an HTMX compatibility bridge covering HTMX 2 and 4 differences.

Beta1 also changed some integration behaviour. New Matrix polling models now install disabled and must be enabled after Matrix credentials and inbound mappings are configured. Existing models retain their state and site customisations on upgrade. Developers and themers are directed to the module's public API and presentation guides, while internal classes, routes and services are not promised as stable extension points.

The module currently requires Drupal 11.4, core Comment and the contributed History module. Canvas integration is optional and requires Canvas 1.10 or later; the beta1 notes say it has been tested through Canvas 1.12.0. ECA Content and Matrix API 3.x are also optional. Although the module includes an HTMX 2/4 compatibility bridge, Drupal 12 compatibility is not yet declared.

Alpha4 Fixes Carry Forward

The beta releases build on fixes delivered in 1.0.0-alpha4 on 20 September. That alpha batched Expand All deliveries, reduced comment-entity loading for context and unchanged refresh requests, restored authorised Edit and Delete actions, improved reading-position behaviour and added a no-JavaScript path for full comment bodies and hidden reply levels.

Alpha4 also added recorded Playwright journeys covering reply revelation, prefetch behaviour and progressive loading with failure recovery. Those changes are now part of a broader beta phase in which the project is refining shared caching, presentation and request behaviour rather than introducing the threaded-discussion model for the first time.

John Locke of Freelock invited feedback from Drupal sites using comments when alpha4 was released, describing the module as a substantial improvement over core comments while asking users to report issues. The beta notes keep that testing posture visible through documented limitations: managed files, custom widgets and custom spam or moderation integrations still require site-specific verification, broader accessibility and cross-browser acceptance remain outstanding, and each placement continues to poll independently.

Advanced Comment Threads therefore has a more defined testing target than it did at alpha4, but the beta designation still matters. For Drupal 11.4 sites evaluating threaded discussions, the latest releases provide a clearer view of the module's loading, caching, accessibility and presentation model while leaving room for further compatibility and acceptance work before a stable 1.0.0 release.