Improve hx-live updates, debounce, and warnings#3907
Open
scriptogre wants to merge 2 commits into
Open
Conversation
scriptogre
force-pushed
the
4.0/improve-hx-live
branch
from
July 21, 2026 14:43
eeca7e3 to
b43a94a
Compare
scriptogre
force-pushed
the
4.0/improve-hx-live
branch
from
July 21, 2026 15:43
b43a94a to
17c46ed
Compare
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.
Description
Follow-up to #3891.
Make sure that in even more scenarios, we skip unnecessary work.
checked,selected, andvalueInput debounce
Rename the
live.inputDebounceMsconfig from #3891 tolive.inputDebounce, and enable both numbers and HCON intervals.Recompute warning
Made the automatic warning appear based on main-thread cost rather than expression count.
Previously, you'd get warnings for 50x (cheap) recompute passes that took e.g. 0.1ms in total (negligible).
Now, you get a warning when one single recompute pass exceeds 16ms (expensive), or recomputes consume over 100ms/s for 2 consecutive seconds.