4grayandClaude Opus 5.5 d8ee38b6d1 fix(workspace): read scroll and focus state before a view's DOM detaches ...

Without the @angular/animations renderer a destroyed view's DOM leaves
before its destroy hooks run, which the deferred removal used to hide. Two
hooks read state from the detached DOM:

- CategoryContentView.ngOnDestroy saved the grid's scrollTop, which reads 0
  once detached, over the offset saved when a card was clicked: back from a
  VOD detail landed at the top of the list (catalog-sorting E2E on every
  OS). The view now keeps the offset of the grid that scrolled last; a grid
  rendered since (a new category's) saves the top.
- Chromium blurs a focused element synchronously while removing it, so
  removing the focused player settings panel fired a focusout without a
  relatedTarget before the panel's destroy hook, which cleared focusInside:
  Escape left focus on the page instead of the tune button
  (player-controls-keyboard web E2E). The panel now judges a focusout a
  microtask later: a removed panel is detached then, while a pointer
  release blurs a panel that stays attached and still drops focus.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-13 09:15:28 +02:00

..

catalog/feature

fix(workspace): read scroll and focus state before a view's DOM detaches

2026-10-13 09:15:28 +02:00

downloads/feature

fix(ui): one focus ring colour everywhere via the shared mixin (#1882)

2026-10-11 10:40:08 +02:00

shared

fix(ui): welcome screens and drop overlay follow the app theme (#1886)

2026-10-11 12:22:23 +02:00

stalker

fix(ui): welcome screens and drop overlay follow the app theme (#1886)

2026-10-11 12:22:23 +02:00

xtream

refactor(storage): seams for server-backed playlist storage (#1896)

2026-10-11 20:03:58 +02:00