4grayandClaude Opus 5.5 9128a90cfd fix(dashboard): keep the hero skeleton until every hero source has loaded ...

The hero dropped its skeleton as soon as the history load resolved empty
and came back moments later with an Xtream recently-added slide (that
query waits for the favorites), moving every rail below by 316 px twice.
On J1 this read renderer.layoutShiftScoreSettled 0.235 on every macOS
iteration and was a race on the Linux runner.

The hero now stays in its skeleton while it has no slide and any of its
sources (history, favorites, Xtream recently added) is on its first load.
DashboardDataService no longer settles xtreamRecentlyAddedLoading before
the playlist inventory has loaded, where "no Xtream playlists" was
decided on a still empty inventory.

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

2026-10-01 06:44:12 +02:00

..

architecture

fix(dashboard): keep the hero skeleton until every hero source has loaded

2026-10-01 06:44:12 +02:00

development

perf(electron): compile the main process and preload for ES2022 (#1757)

2026-09-30 18:48:35 +02:00

maintenance

ci(test): type-check Jest spec programs and gate it in CI (#1705)

2026-09-27 20:54:27 +02:00

superpowers

feat(epg): rebuild the programme guide for M3U playlists (#1560)

2026-09-06 18:47:25 +02:00