Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: clear reference to element removed from split-layout #7367

Merged
merged 1 commit into from
Apr 29, 2024

Conversation

web-padawan
Copy link
Member

Description

Fixes vaadin/flow-components#6248

Currently, when removing an element from split-layout, the _primaryChild or _secondaryChild reference isn't updated.

As a result, track event is handled and splitter-dragend is fired, which is then handled by the Flow counterpart.
The error is thrown by this logic which relies on both primary and secondary components to be available.

Added logic to clear the reference along with removal of the corresponding slot and a test to check the event isn't fired.

Type of change

  • Bugfix

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@web-padawan web-padawan merged commit e7aba8b into main Apr 29, 2024
9 checks passed
@web-padawan web-padawan deleted the fix/split-layout-remove-track branch April 29, 2024 09:20
web-padawan added a commit that referenced this pull request Apr 29, 2024
)

Co-authored-by: Serhii Kulykov <iamkulykov@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SplitLayout: Splitter leads to JS exceptions, when a component has been removed
3 participants