I'd like to just follow up on the status of this bug. I notice the github issue has been closed. Does this mean this bug has been fixed? I tried it again on your demo
, but still find the same bug.
Also, we are getting feedback from our user encountering similar problem when deleting un-adjacent cells. Our user expresses interest to delete a group of values separated by disabled cell (see attached image, the gray cells are disabled). If he select the whole area and hit delete, nothing happens because the disabled cells, if he select un-adjacent cells, the following bug occurs.
Steps to reproduce:
1. Setup a spreadsheet using datasource
2. select un-adjacent cells, A1, A3
3. hit delete
Expected: Cell values are deleted
Actual: Cell values look like they are deleted, however, on enter value in A4, the values in A1 and A3 come back again.
This delete bug cannot be reproduced on the simple demo on your website - I'm not sure why no error is logged in console for the demo. However, in our instance, the following error is reported: "Unsupported for multiple ranges". I can trace the problem back into the values function throwing error if ref is instanceof UnionRef. The problem for us is that our spreadsheet uses Datasource for binding, the throw cause values function abandon all execution below, which including lines that should notify datasource about value changes. This the why the values come back again.
Could Kendo support either
a. deleting values across un-adjacent cells, or
b. deleting values of editable cells when disabled cells are also in selection?
I'm also curious why avoiding UnionRef? What will be the consequence of removing that error check?