Skip to content

fix(flow-client): loading state muting based on trigger events (#24230) (CP: 25.1)#24335

Merged
vaadin-bot merged 1 commit into
25.1from
cherry-pick-24230-to-25.1-1778670878485
May 13, 2026
Merged

fix(flow-client): loading state muting based on trigger events (#24230) (CP: 25.1)#24335
vaadin-bot merged 1 commit into
25.1from
cherry-pick-24230-to-25.1-1778670878485

Conversation

@vaadin-bot
Copy link
Copy Markdown
Collaborator

This PR cherry-picks changes from the original PR #24230 to branch 25.1.

Original PR description

Fixes #24075

This change reverts the eager removal of loading state introduced by #23229, as it causes the indication to disappear during ongoing loading. As a replacement, it re-introduces debouncing tracking of active requests, and adds event-based silencing of the loading indication to avoid flashing the indicator for high-frequency UI interactions.

In addition, instead of setting loading state using ConnectionState.setState() directly, the proper connection state methods (loadingStarted(), loadingFinished()) are used to avoid interference with loading state for requests from other sources outside Flow client.

Fixes #24075

This change reverts the eager removal of loading state introduced by
#23229, as it causes the indication to disappear during ongoing loading.
As a replacement, it re-introduces debouncing tracking of active
requests, and adds event-based silencing of the loading indication to
avoid flashing the indicator for high-frequency UI interactions.

In addition, instead of setting loading state using
`ConnectionState.setState()` directly, the proper connection state
methods (`loadingStarted()`, `loadingFinished()`) are used to avoid
interference with loading state for requests from other sources outside
Flow client.

---------

Co-authored-by: Marco Collovati <marco@vaadin.com>
Co-authored-by: Mikhail Shabarov <61410877+mshabarov@users.noreply.github.com>
@sonarqubecloud
Copy link
Copy Markdown

@vaadin-bot
Copy link
Copy Markdown
Collaborator Author

This PR is eligible for auto-merging policy, so it has been approved automatically. If there are pending conditions, auto merge (with 'squash' method) has been enabled for this PR [Message is sent from bot]

@vaadin-bot vaadin-bot enabled auto-merge (squash) May 13, 2026 11:24
@github-actions
Copy link
Copy Markdown

Test Results

 1 391 files  + 2   1 391 suites  +2   1h 26m 12s ⏱️ +52s
10 035 tests +10   9 965 ✅ +10  70 💤 ±0  0 ❌ ±0 
10 508 runs  +10  10 429 ✅ +10  79 💤 ±0  0 ❌ ±0 

Results for commit bd1fa51. ± Comparison against base commit de7942d.

@vaadin-bot vaadin-bot merged commit d88a521 into 25.1 May 13, 2026
29 checks passed
@vaadin-bot vaadin-bot deleted the cherry-pick-24230-to-25.1-1778670878485 branch May 13, 2026 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants