Test case: http://live.datatables.net/mojolena/1/edit (note: disable CORS to use)
Using the disable method on a field (e.g. select) disables the field and prevents user input on that field.
I have several nested Datatable editors which i would like to disable in similar fashion.
However, using disable on those fields:
1. Gives an error:
dataTables.editor.min.js:1 Uncaught TypeError: Cannot read property 'prop' of undefined
as if the field is undefined, where as i can clearly see it is defined using the fields method.
Furthermore, if changed from datatable to select type gives no issues.
2. Sets the styles for a disabled field (e.g. greyed text and border) but user interactivity is not blocked (e.g. buttons are visible, can be clicked and forms for new, edit and edit are opened).
Is this a bug or perhaps not implemented?