We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If a layout implements HasReadOnly, any component added while it is read-only, should result in the component being switched to read-only as well.
HasReadOnly
However, if a layout is not read-only, adding read-only component should not switch the state off.
The text was updated successfully, but these errors were encountered:
#403 fixed
d359b8c
#402 #403 #404 done (#405)
d4406ef
fixed layout bugs, added SuperCheckbox
Release 0.14.1 ready (#411)
2922a06
* #400 #406 #408 #402 #403 #404 done (#405) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: vaadin-miki <vaadin-miki@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
vaadin-miki
Successfully merging a pull request may close this issue.
If a layout implements
HasReadOnly
, any component added while it is read-only, should result in the component being switched to read-only as well.However, if a layout is not read-only, adding read-only component should not switch the state off.
The text was updated successfully, but these errors were encountered: