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
Originally posted by jiawang1 September 5, 2024
Hi colleague:
When I set readonly to multiInput component, the close button for the token in the input field will disappear. However, the close button for the token in the dropdown will still be visible and will react to user clicks. although it does not really delete the token from the menu.
I have noticed the notes: "A read-only component can not be deleted or selected, but still provides visual feedback upon user interaction." So I did not report this as a bug. Just want to confirm is this the expected design? I think click close button but nothing happen will confuse the user.
Regards
Jay
Hello @SAP/ui5-webcomponents-topic-rl ,
As you can seen in the discussion the tokens inside ui5-multi-input has close button when the component is set to readonly mode. EXAMPLE
Could you please check?
Regards,
Nayden
The text was updated successfully, but these errors were encountered:
Discussed in #9825
Originally posted by jiawang1 September 5, 2024
Hi colleague:
When I set readonly to multiInput component, the close button for the token in the input field will disappear. However, the close button for the token in the dropdown will still be visible and will react to user clicks. although it does not really delete the token from the menu.
I have noticed the notes: "A read-only component can not be deleted or selected, but still provides visual feedback upon user interaction." So I did not report this as a bug. Just want to confirm is this the expected design? I think click close button but nothing happen will confuse the user.
Regards
Jay
Hello @SAP/ui5-webcomponents-topic-rl ,
As you can seen in the discussion the tokens inside ui5-multi-input has close button when the component is set to readonly mode. EXAMPLE
Could you please check?
Regards,
Nayden
The text was updated successfully, but these errors were encountered: