Show a stable loading state before the first render - #639
Open
rosenrot00 wants to merge 3 commits into
Open
Conversation
rosenrot00
marked this pull request as ready for review
August 29, 2026 16:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
layout.height, falling back to the existing 285 px defaultaria-busyand respectprefers-reduced-motionfinallyblock so rendering errors do not leave the card looking permanently busyThe plot container has no height before the first
Plotly.react()call and is hidden during that time. Cards can therefore appear missing and then cause a visible layout shift when history or statistics data arrives.This adds a CSS-only loading state. It does not trigger another Plotly render or any additional Home Assistant data request.