Overriding theme for sub elements
nbabb opened this issue · 1 comments
We have certain global theme changes for input fields that are causing the multi-select component to have rendering issues. I am able to affect styling up to a point, but am not able to remove the border on the input-field I indicate in this screencast https://prnt.sc/v5dgzo
My understanding, after discussing with Vaadin folks, is that I would need to use theme propogation (as discussed here https://vaadin.com/docs/v14/themes/styling-components.html#sub-components) to target nested components. Does the multi-select-combo-flow component support this? I'm not sure that it does, given that it doesn't implement HasTheme? Do you have recommendations for me on this?
One option is for us to revert our component to vaadin defaults, so that the multi-select component fits in, but I'm not sure if that will be an option for us, given other complementary styling changes that have occurred. I suppose another option might be to make the input style changes applicable with a theme (so that some of the effects of our styling changes are isolated). But that still leaves us with the multi-select needing certain styles in subcomponents - in order to blend in - that might not be possible (like making the background color of the input white, for example).
Any suggestions are appreciated. Thanks!
And some off topic questions:
- Is there a way to control the order of the selected items (note order might not be lexical)?
- Can you control the backspace behavior for deletion? It seems a little too easy to delete items with backspace.
- Can the required indicator be customized? We use the asterisk before the label where your component has a dot after.
- When multiple values are selected in the component, and the values wrap, eventually the dropdown will cover the "Choose" box, until it is dismissed. Seems like you'd want the combo to shift to always be at the bottom. Or maybe have an option where the Combo is always at the beginning?
- Seems that in compact mode you lose the ability to type (and filter) in the component. Is there a way around this? Wondering what the reason is for taking away this capability in compact mode.
Any update on this?