-
Notifications
You must be signed in to change notification settings - Fork 161
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
Update enabled status for virtual children of Element without Component #6315
Conversation
IT tests is provided here: vaadin/vaadin-grid-flow#750 |
return checkParentChainState(parentComponent); | ||
Element parent = element.getParent(); | ||
if (parent != null) { | ||
if (isAttachedToParent(element, parent)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you merge this PR so, that the merge commit contains a short explanation of how this fixes the issue? It is not immediately obvious and might be nice to have a record.
Reviewed 1 of 2 files at r1.
Reviewable status: 1 unresolved discussion, 1 of 1 LGTMs obtained (waiting on @denis-anisimov)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 1 of 2 files at r1.
Reviewable status: 1 unresolved discussion, 1 of 1 LGTMs obtained (waiting on @denis-anisimov)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dismissed @vaadin-bot from a discussion.
Reviewable status: complete! all discussions resolved, 1 of 1 LGTMs obtained
…nt (#6315) ComponentUtil::onComponentAttach/ComponentUtil::onComponentDetach should use Element API parent to decide whether to call Component::onEnabledStateChanged. That allows to use correct parent in case there is no Component mapped to Element. Fixes vaadin/vaadin-grid-flow#687
(#6315) ComponentUtil::onComponentAttach/ComponentUtil::onComponentDetach should use Element API parent to decide whether to call Component::onEnabledStateChanged. That allows to use correct parent in case there is no Component mapped to Element. Fixes vaadin/vaadin-grid-flow#687 # Conflicts: # flow-server/src/test/java/com/vaadin/flow/component/ComponentTest.java
(#6315) ComponentUtil::onComponentAttach/ComponentUtil::onComponentDetach should use Element API parent to decide whether to call Component::onEnabledStateChanged. That allows to use correct parent in case there is no Component mapped to Element.
…nt (#6315) ComponentUtil::onComponentAttach/ComponentUtil::onComponentDetach should use Element API parent to decide whether to call Component::onEnabledStateChanged. That allows to use correct parent in case there is no Component mapped to Element. Fixes vaadin/vaadin-grid-flow#687
(#6315) ComponentUtil::onComponentAttach/ComponentUtil::onComponentDetach should use Element API parent to decide whether to call Component::onEnabledStateChanged. That allows to use correct parent in case there is no Component mapped to Element. Fixes vaadin/vaadin-grid-flow#687 # Conflicts: # flow-server/src/test/java/com/vaadin/flow/component/ComponentTest.java
(#6315) ComponentUtil::onComponentAttach/ComponentUtil::onComponentDetach should use Element API parent to decide whether to call Component::onEnabledStateChanged. That allows to use correct parent in case there is no Component mapped to Element.
* IT test for #687 and vaadin/flow#6315 PR.
Fixes vaadin/vaadin-grid-flow#687
This change is