docs(forms): clarify debounce('blur') usage with custom FormValueControl#69382
Open
erkamyaman wants to merge 1 commit into
Open
docs(forms): clarify debounce('blur') usage with custom FormValueControl#69382erkamyaman wants to merge 1 commit into
erkamyaman wants to merge 1 commit into
Conversation
A custom FormValueControl only participates in debounce('blur') if it emits
the touch output on the native blur event. This was undocumented, and the
touch name reads like a focus event, so users wired it to (focus) and
blur-based debouncing silently did nothing.
Add a dedicated guide section with a working example, link the debounce API
reference to it, and clarify the touch JSDoc that it must fire on blur, not
focus.
Fixes angular#69370
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.
A custom FormValueControl only participates in debounce('blur') if it emits the touch output on the native blur event. This was undocumented, and the touch name reads like a focus event, so users wired it to (focus) and blur-based debouncing silently did nothing.
Add a dedicated guide section with a working example, link the debounce API reference to it, and clarify the touch JSDoc that it must fire on blur, not focus.
Fixes #69370
PR Checklist
Please check that your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #69370
What is the new behavior?
Documents
debounce('blur')with a customFormValueControl: a guide example, a@seelink from thedebounceAPI, and a clarifiedtouchJSDoc (emit onblur, notfocus). Full context in #69370Does this PR introduce a breaking change?