Passive event listeners are a new feature in the DOM spec that enable developers to opt-in to better scroll performance by eliminating the need for scrolling to block on touch and wheel event listeners. Developers can annotate touch and wheel listeners with {passive: true} to indicate that they will never invoke preventDefault. This feature shipped in Chrome 51, Firefox 49 and landed in WebKit. For full official explanation read more here.
See also: What are passive event listeners?
You may have to wait for your .js library to implement support.
If you are handling events indirectly via a JavaScript library, you may be at the mercy of that particular library's support for the feature. As of August 2016, it does not look like any of the major libraries have implemented support. Some examples:
That's the original data fiddle we used all the way through, and when i tried it didnt work for me, so i kept the original fiddle as is. Please point me where to amend the code in this fiddle.
Answers
I've not seen that message before. Do you get the error in this example?
https://datatables.net/examples/basic_init/zero_configuration.html
Kevin
i tried to add
passive: 'false'
-- see below -- what others are saying.
For those receiving this warning for the first time, it is due to a bleeding edge feature called Passive Event Listeners that has been implemented in browsers fairly recently (summer 2016). From https://github.com/WICG/EventListenerOptions/blob/gh-pages/explainer.md:
Passive event listeners are a new feature in the DOM spec that enable developers to opt-in to better scroll performance by eliminating the need for scrolling to block on touch and wheel event listeners. Developers can annotate touch and wheel listeners with {passive: true} to indicate that they will never invoke preventDefault. This feature shipped in Chrome 51, Firefox 49 and landed in WebKit. For full official explanation read more here.
See also: What are passive event listeners?
You may have to wait for your .js library to implement support.
If you are handling events indirectly via a JavaScript library, you may be at the mercy of that particular library's support for the feature. As of August 2016, it does not look like any of the major libraries have implemented support. Some examples:
jQuery.js - ongoing issue: https://github.com/jquery/jquery/issues/2871
React.js - ongoing issue: https://github.com/facebook/react/issues/6436
Hammer.js - ongoing issue: https://github.com/hammerjs/hammer.js/pull/987
perfect-scrollbar - ongoing issue: https://github.com/noraesae/perfect-scrollbar/issues/560
AngularJS - ongoing issue: https://github.com/angular/angular.js/issues/15901
If you scroll to next page in parent grid, the child grid is still showing previously selected corresponding record in child grid.
You would need to do the same thing we did with the
searchby using thepageevent.Kevin
Hi Kevin, Many thanks, would you be able to amend the data fiddle you provided as an example earlier please.
Please see the link below:
live.datatables.net/biliniyu/1/edit
I'm not sure I understand what you want me to do.
Kevin
That's the original data fiddle we used all the way through, and when i tried it didnt work for me, so i kept the original fiddle as is. Please point me where to amend the code in this fiddle.
live.datatables.net/biliniyu/1/edit
We discussed many things. What specifically do you want amend and what is not working for you?
Kevin
Hi Kevin,
My apologies, this part of the query
See this example for clearing the table when going to the next page:
http://live.datatables.net/cirelube/1/edit
Kevin