Internet Explorer 11, FixedHeader and search
Internet Explorer 11, FixedHeader and search
NiKa
Posts: 3Questions: 1Answers: 0
Hey there Folks,
I have a serious problem! First of all here is the problem on live.datatables
http://live.datatables.net/piwiteja/1/
This works flawlessly on firefox, but when it comes to the good old IE 11, it seems like fixedheader together with search won't work... To reproduce the problem, just click on one of the input search fields and start typing. First letter works, but then after .draw() is called, it drops out of the input field and you have to click on it again OR which is way worse, it stays in the input field but you can't type anymore (it seems like it still recognizes you typing since (with some console.log) you can see the outputs on the console, but the screen just won't refresh or won't recognize new letters. Only thing that helps is to click out of the input field where ever you want and then focus it again....
I am really stuck with this one.... If you need anymore facts/ inputs, feel free to ask. I already tried a lot...
Thanks for future answers 
Best
Nikolai
Answers
This was also reported just a few days ago on github. Its certainly a bug that needs to be fixed.
Allan
Do you have any clue why this bug appears?
What I found out right now is, that it has something to do with the .draw() method regardless of any search. So you can indeed call any search method on the column, but once you call .draw() it gets stuck. Of course only when you have fixedHeader activated. Weird thing is, when you try the same thing on the fixedFooter, after typing a letter it blurs out of the input, draws the new table and you can type again (after clicking the input field again)
No not yet, I've not had a chance to look into it I'm afraid. It might be caused by FixedHeader being reattached to the document on draw and IE not coping very well with that.
Allan
Yeah, this could be. It feels like a new header is placed onto the old one. I might have a look into it.
It isn't a new one replacing an old one, but rather the existing one being reinserted into the DOM. Perhaps a simple check to see if it needs to be inserted when it is would fix the IE issue.
Allan