Link to test case:
http://live.datatables.net/noyidohu/3/edit
Description of problem:
In our application we have multiple DataTables instances. We recently tried to upgrade from an older version of DataTables and the Editor and ran into problems with calling draw() on one DataTable instance affecting unrelated DataTables instances.
Our current versions are:
DataTables 1.10.18, Editor 1.7.4, Buttons 1.5.2, Select 1.2.6
We're trying to upgrade to the current versions:
DataTables 1.10.23, Editor 1.9.6, Buttons 1.6.5, Select 1.3.1
In the linked example code there are two DataTables. The first one is just a simple DataTables instance. The second is a DataTable and the related Editor. The second DataTable has a single date field that is of type datetime. The example code has an interval calling draw() on the first of the two DataTables every five seconds. In order to actually see the problem you'll have to open the live preview into its own window with the arrow button at the top right of the output panel. For some reason it behaves differently as a panel (possibly also a bug?). Once you do that, click the "New" button for the second DataTable. By default it will set the focus to the only field (the date) which will open the calendar widget. Once the calendar widget appears, the next time that draw() is called on the first table (you can watch the log for that in the browser debug console) the calendar widget will disappear. Click back in the date field and it will disappear again the next time draw is called on the first (unrelated) table. In our application we have a DataTable that is always shown that updates on a two second interval. This makes using the calendar widget nearly impossible as it is constantly disappearing as we're trying to select a date.
All that said, if you comment out this line in the first DataTable configuration:
scrollY: 200,
then the problem goes away. We do however need to set that flag though so removing it won't work for us.
Is there a way to keep the two DataTables from interacting? Is this a bug? Are we doing something wrong? We'd really like to upgrade and make use of some of the newer DataTables features and are hoping there's a fix or workaround for this issue.
Thanks.