Thanks for the updates you have made. If you dont mind me highlighting some few issues again.
Multiple mode: When you click on the select, detect if the data-table is open, if the data-table is open then close it. Currently opening of the data-table happens when you click the select, but then you have to click the close button to close it.
Multiple mode: Add an Ok/Apply button at the bottom left of the data-table. This Ok button should show when you have activated "multiple" mode. Usually one selects items on the left and now having to scroll to the right to close the data-table is additional work. This ok/apply button will close the data-table once a user has made their selection and clicked "Ok"
No two way binding when one actually clicks the "delete" button on the chip itself. This works when items are de-selected from the data-table not the other way round.
The v-model returns objects whilst the select return item-values. Can you please look at that. For example I have a label here that is supposed to show the vmodel values in {{ selItems }}, when an item is selected, its object is returned as demonstrated. The values in the select are Ok though.
The location of the data-table should always syncronise itself with the select. For example in the gif above, the select moved down whilst the data-table did not and thus sat itself on top of the select.
Hi there
Thanks for the updates you have made. If you dont mind me highlighting some few issues again.
Multiple mode: When you click on the select, detect if the data-table is open, if the data-table is open then close it. Currently opening of the data-table happens when you click the select, but then you have to click the close button to close it.
Multiple mode: Add an Ok/Apply button at the bottom left of the data-table. This Ok button should show when you have activated "multiple" mode. Usually one selects items on the left and now having to scroll to the right to close the data-table is additional work. This ok/apply button will close the data-table once a user has made their selection and clicked "Ok"
No two way binding when one actually clicks the "delete" button on the chip itself. This works when items are de-selected from the data-table not the other way round.