docs(forms): clarify debounce('blur') usage with custom FormValueControl by erkamyaman · Pull Request #69382 · angular/angular
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:
- The commit message follows our guidelines: https://github.com/angular/angular/blob/main/contributing-docs/commit-message-guidelines.md
- Tests for the changes have been added (for bug fixes / features)
- Docs have been added / updated (for bug fixes / features)
PR Type
What kind of change does this PR introduce?
- Bugfix
- Feature
- Code style update (formatting, local variables)
- Refactoring (no functional changes, no api changes)
- Build related changes
- CI related changes
- Documentation content changes
- Other
What is the current behavior?
Issue Number: #69370
What is the new behavior?
Documents debounce('blur') with a custom FormValueControl: a guide example, a @see link from the debounce API, and a clarified touch JSDoc (emit on blur, not focus). Full context in #69370
Does this PR introduce a breaking change?
- Yes
- No