This repository was archived by the owner on Sep 5, 2024. It is now read-only.
fix(chips): unwanted re-focus of last chip after blur #11305
Merged
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.
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?
As described by @caseyjhol, "With
md-add-on-blur
enabled, clicking outsidemdChips
or selecting another input element results in the previously focusedmdChips
being highlighted again. This is especially jarring on a mobile device (e.g. type in some text for the chip, scroll down to the next form element, select it, and then the chip is added butmdChips
is then scrolled back into position and focused). It's also not possible to tab to the next element."Issue Number:
Fixes #10758
What is the new behavior?
this solves a regression introduced in 1.1.2 by #9650
change
ng-change
demo to use$log
instead ofalert
fix some lint line length warnings
JSDoc clean up
Does this PR introduce a breaking change?
Other information