refactor: remove iron-resize event from field-mixin #3213
Merged
Conversation
This file contains 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
|
Kudos, SonarCloud Quality Gate passed!
|
web-padawan
approved these changes
Dec 21, 2021
36 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Part of #331
<vaadin-text-area>or other fields no longer need to dispatch the "iron-resize" event. Container components, such as<vaadin-tabs>or<vaadin-grid>use internal resize observers and automatically react to child resizes.Here's an example, where a
<vaadin-text-area>is placed inside the row details of<vaadin-grid>. Typing into the field expands it and the field is marked invalid using a timeout. In both cases, the grid automatically notices the size (row height) change and repositions its rows:Kapture.2021-12-21.at.14.33.03.mp4