In this example there are two comboboxes where the second depends on selection of the first one.
In the first/left combobox a field is chosen (like “Name”).
The second/right combobox shows all values available about this field (like “Sara”, “Tobias”, etc.).
The second combobox has a disabled-definition looking for the first combobox to have a selection. If nothing is selected in the first, then disable the second. Vice versa.
That’s basically working fine through angular signals.
Before the problem itself is stated, one more basic about the combox’ close behavior.
When the second combobox is opened it will automatically close after losing its focus, e.g. when one clicks into the first combobox or clicks the X-Chip of the first combobox.
The actual problem occurs, when the combobox’ disabled-defintion comes together with the focus loss. This only happens when clicking the X-Chip of the first Combobox. This causes a focus loss and the activation of the disabled-definition as well.
It seems that the disabling happens first and prevents the focus loss from automatically close the still opened second combobox. It gets disabled but stays open.
This happens only when having the select all option enabled.
https://codepen.io/Sebastian-Krings/pen/jEqROqv
Hi @SebastianKrings , I'd suggest creating an issue on the Calcite GitHub site, this is a space for ArcGIS Maps SDK for JavaScript ideas not reporting Calcite design system bugs.
https://github.com/Esri/calcite-design-system
We initially created a support case against esri (#04066009). They asked us to create ideas instead.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.