1c48c11ac0168d9598795641b4fc337a2233289e Fix: Don't modify the display array in -api row().remove() - it should wait for the next draw

This relates to DataTables/DataTablesSrc#269
and is fairly nuanced - it boils down to the fact that the display array
should reflect what is shown in the table, and deleting a value from it
will cause an index offset. The other option might be to make the
element null, as happens with the master, but that would be a change in
type and I'm not certain everything could handle that. The array will
regenerate on the next draw, so it is properly in sync with what is
drawn now.

Sync to source repo @1c48c11ac0168d9598795641b4fc337a2233289e

Author: dtbuild

datatables.json

@@ -11,5 +11,5 @@
     ],
     "src-repo": "http://github.com/DataTables/DataTablesSrc",
     "last-tag": "2.0.4",
-    "last-sync": "d04853a9ab4fb7e9f5b4acfc1fea81f5952116e8"
+    "last-sync": "1c48c11ac0168d9598795641b4fc337a2233289e"
 }

js/dataTables.js

@@ -7812,11 +7812,6 @@
 				settings.aiDisplayMaster.splice(idx, 1);
 			}
 
-			idx = settings.aiDisplay.indexOf(row);
-			if (idx !== -1) {
-				settings.aiDisplay.splice(idx, 1);
-			}
-	
 			// For server-side processing tables - subtract the deleted row from the count
 			if ( settings._iRecordsDisplay > 0 ) {
 				settings._iRecordsDisplay--;

js/dataTables.min.js

@@ -7759,11 +7759,6 @@ _api_registerPlural( 'rows().remove()', 'row().remove()', function () {
 			settings.aiDisplayMaster.splice(idx, 1);
 		}
 
-		idx = settings.aiDisplay.indexOf(row);
-		if (idx !== -1) {
-			settings.aiDisplay.splice(idx, 1);
-		}
-
 		// For server-side processing tables - subtract the deleted row from the count
 		if ( settings._iRecordsDisplay > 0 ) {
 			settings._iRecordsDisplay--;