Gantt View Remains Constrained After Task Deselection

[manuvarkey]

What problem does this solve

When a task is selected in the Task Table, the Gantt view becomes constrained to the selected task and does not allow scrolling beyond the task's bounds.

This constraint remains active even after the task is deselected using the <Escape> key.

This issue is not observed when selecting a task directly in the Gantt view.

Expected behavior

When a task is selected in the Task Table, the Gantt view should scroll to the selected task. However, after doing so, it should retain normal scrolling behavior and allow navigation across the full timeline.

Steps to reproduce

1. Select a task in the Task Table.
2. The Gantt view becomes constrained to the selected task's bounds.
3. Press <Escape> to deselect the task.
4. The task is visually deselected, but the Gantt view remains constrained and cannot be scrolled beyond the previously selected task's bounds.

Screencast

Screencast.from.2026-09-10.22-43-45.mp4

---

Type: Bug · Open Planner Studio v2026.9.0 · Linux x86_64 · en

[Nozzit]

Thanks for the clear report and the screencast, that made this easy to pin down.

Cause. A plain click in the task table sends a "reveal" request to the Gantt canvas so the bar scrolls into view when it is offscreen. The effect that handles that request depends on the shared time axis, which is rebuilt on every horizontal scroll. So the same request was re-applied on every scroll, pulling the bar back into view each time. That is why the timeline felt clamped to the last clicked task, and why Escape did not help: deselecting cleared the selection but not the request. Selecting a task directly in the Gantt never goes through this path, which matches what you observed.

Fix. The reveal request is now handled exactly once; only a new click triggers a new reveal. A browser regression test covers the exact steps from your report (click in the table, Escape, scroll back with the mouse wheel) and fails without the fix.

The fix is in #131 and will be part of the next release. If you still see the timeline stick after updating, please reopen this issue.

---

This issue was analysed and fixed with AI assistance (Claude Code); the change was verified with the repository's own test suite.

---

Generated by Claude Code