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
Viewing the comparable React component example, the React library does have a pointer cursor when hovering on the icon. This is consistent with the other visually similar components such as ComboBox.
This seems to primarily be caused by the setting of pointer-event to none on this line:
In my local testing I see no harm from removing this style, but it seems so intentionally put there that I worry I am missing something. Do we know why pointer-events were sometimes disabled for the MultiSelect icon? Other components like the Svelte ComboBox that have similar structures and styles don't have this style. Is the line just a bug or is there something deeper lurking behind it?
I could generate a PR to remove the line and restore the pointer cursor but am hesitant since I feel like I'm missing something.
The text was updated successfully, but these errors were encountered:
As can be in the filterable multiselect example from the docs site, hovering over the expander icon retains the text input cursor instead of switching to a pointer cursor.
Viewing the comparable React component example, the React library does have a pointer cursor when hovering on the icon. This is consistent with the other visually similar components such as ComboBox.
This seems to primarily be caused by the setting of pointer-event to none on this line:
carbon-components-svelte/src/MultiSelect/MultiSelect.svelte
Line 469 in 57b6ea6
In my local testing I see no harm from removing this style, but it seems so intentionally put there that I worry I am missing something. Do we know why pointer-events were sometimes disabled for the MultiSelect icon? Other components like the Svelte ComboBox that have similar structures and styles don't have this style. Is the line just a bug or is there something deeper lurking behind it?
I could generate a PR to remove the line and restore the pointer cursor but am hesitant since I feel like I'm missing something.
The text was updated successfully, but these errors were encountered: