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
Describe the bug The updated MultiSelectTree rendering and output do not show the placeholder text:
To reproduce Run the Empty MultiSelectTree test
Expected behavior The MultiSelectTree... text should be visible in the input-like element.
MultiSelectTree...
Affected suites (please remove the unneeded items)
Additional context The issue comes from the width: 100% style for the k-input-values selector. Potential fix that needs further testing could be:
width: 100%
k-input-values
.k-input-values { width: auto; max-width: 100%; }
The text was updated successfully, but these errors were encountered:
+1
Sorry, something went wrong.
The issue comes from the width: 100% style for the k-input-values selector. Potential fix that needs further testing could be: .k-input-values { width: auto; max-width: 100%; }
The issue comes from the width: 100% style for the k-input-values selector. Potential fix that needs further testing could be:
Using this workaround, the clear button is no longer pushed to the far right.
This rule worked for me: .k-input-values:not(:has( * )) /* the taglist does not have any children (chips) */
Update: After updating to 14.2, that rule doesn't work for me anymore. Now using: .k-input-values:has(~ .k-input-inner)
Fixed with a04fad2
inikolova
No branches or pull requests
Describe the bug
The updated MultiSelectTree rendering and output do not show the placeholder text:
To reproduce
Run the Empty MultiSelectTree test
Expected behavior
The
MultiSelectTree...
text should be visible in the input-like element.Affected suites (please remove the unneeded items)
Additional context
The issue comes from the
width: 100%
style for thek-input-values
selector. Potential fix that needs further testing could be:The text was updated successfully, but these errors were encountered: