After fixing #34, now items are not deleted in the back-end. However, one or more items can still disappear for a split second when clicking the close button or backspacing (even though they are correctly returned into the UI after processing the events).
There are also: a close button, a focus indicator (blue underline) and a hand cursor, which seem to indicate that the user can interact with the compent (but they can't. because the component is in read-only mode).
Among other things, this issue is caused because the readonly setting only affects the paper-input part, but backspace is handled by paper-chip-input-autocomplete (which doesn't consider whether read-only mode is set).
Perhaps, we can achieve a better UX by treating readonly as "disabled" (which is correctly implemented by the client-side component) but with normal opacity.
After fixing #34, now items are not deleted in the back-end. However, one or more items can still disappear for a split second when clicking the close button or backspacing (even though they are correctly returned into the UI after processing the events).
There are also: a close button, a focus indicator (blue underline) and a hand cursor, which seem to indicate that the user can interact with the compent (but they can't. because the component is in read-only mode).
Among other things, this issue is caused because the readonly setting only affects the
paper-input
part, but backspace is handled by paper-chip-input-autocomplete (which doesn't consider whether read-only mode is set).Perhaps, we can achieve a better UX by treating readonly as "disabled" (which is correctly implemented by the client-side component) but with normal opacity.![image](https://user-images.githubusercontent.com/11554739/109344727-e2ee1200-784d-11eb-8028-315f51731029.png)