Kabiru Mwenja 5fdf57df69 Defer activity-tab sequence_version to anchor resolution ...

The work package activity tab computed a per-journal sequence_version on
every render — a ROW_NUMBER() window function over a LATERAL join — only to
stamp the legacy data-anchor-activity-id that #activity-N deep links rely on.
Nothing mints those links anymore; copy and share links use
#comment-<journal id>, which needs no extra query.

The activity number is now resolved on demand. Only a request carrying
?anchor=activity-N runs the window function, mapping the number to a journal
id the paginator exposes as resolved_anchor. The view hands that to the
client, which rewrites #activity-N to the canonical #comment-<id> and scrolls
using the comment anchor already present in the DOM. Default renders no longer
touch the window function.

References WP #68063.

2026-06-05 14:26:04 +03:00

..

activities_spec.rb

Defer activity-tab sequence_version to anchor resolution

2026-06-05 14:26:04 +03:00

activity_tab_comment_editor_spec.rb

Use capybara rich text selector for label assertion

2025-05-16 13:22:51 +03:00

emoji_reactions_spec.rb

Freeze string literals in specs

2025-05-05 09:29:55 +02:00

internal_comments_spec.rb

Fix internal comment checkbox state not persisting across tab navigation

2025-09-23 19:04:46 +03:00

revision_component_spec.rb

Update Ruby copyright headers using rake task

2025-03-18 14:23:54 +01:00