You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When calling setVisible(false) on e.g. "Delete" button of the CRUD, the teleporting logic doesn't work because:
The vaadin-button doesn't have slot attribute on the client side due to setVisible(false) (as that prevents Flow from sending updates to the client by design),
The _deleteButton property on the web component is empty as it's set based on the slotted node presence,
The corresponding check fails and there are no elements teleported at all (notably, there is no error / warning shown either).
Expected outcome
Expected all the elements but the missing button to be teleported as usual.
This could be probably done by changing the web component to not check for any of the buttons if _noDefaultButtons flag added in vaadin/web-components#7181 is used (which was specifically added for Flow counterpart).
Minimal reproducible example
crud.getDeleteButton().setVisible(false);
Steps to reproduce
Add the line above after adding a CRUD to the view.
Make sure the default (dialog) editor position is used.
Press "New" button to open a dialog - it will be empty
Environment
Vaadin version(s): 24.x
Browsers
Issue is not browser related
The text was updated successfully, but these errors were encountered:
Description
When calling
setVisible(false)
on e.g. "Delete" button of the CRUD, the teleporting logic doesn't work because:vaadin-button
doesn't haveslot
attribute on the client side due tosetVisible(false)
(as that prevents Flow from sending updates to the client by design),_deleteButton
property on the web component is empty as it's set based on the slotted node presence,Expected outcome
Expected all the elements but the missing button to be teleported as usual.
This could be probably done by changing the web component to not check for any of the buttons if
_noDefaultButtons
flag added in vaadin/web-components#7181 is used (which was specifically added for Flow counterpart).Minimal reproducible example
Steps to reproduce
Environment
Vaadin version(s): 24.x
Browsers
Issue is not browser related
The text was updated successfully, but these errors were encountered: