See my last two posts in this thread. Basically Chrome and maybe other browser's will auto-populate the first input field it finds. A good workaround seems to be to place a dummy/hidden input field at the top of the page and this will be populated instead of the Datatables search input.
I found out a little while ago that they starting doing this nonsense as sites were abusing the autocomplete="false" attribute, attempting to disallow password managers for filling in the user's details for them. So to benefit the users, they ignore that attribute. This looks like an unindented consequence.
Answers
@andreitofan
See my last two posts in this thread. Basically Chrome and maybe other browser's will auto-populate the first
inputfield it finds. A good workaround seems to be to place a dummy/hidden input field at the top of the page and this will be populated instead of the Datatables search input.Kevin
I found out a little while ago that they starting doing this nonsense as sites were abusing the
autocomplete="false"attribute, attempting to disallow password managers for filling in the user's details for them. So to benefit the users, they ignore that attribute. This looks like an unindented consequence.Allan
Hello I found the following solution that works in Chrome march 2024
initComplete: function() {$(this.api().table().container()).find('input').attr('autocomplete', 'off');$(this.api().table().container()).find('input').val('');},Super - thank you for the update.
Allan