Editor & Responsive plugin - IE8 Compatibility broken in latest

dataagility

Test Case is the DT example site:
https://editor.datatables.net/examples/extensions/responsive.html

Debug:
https://debug.datatables.net/uxelus

Tested on MS VM Windows 7 IE8.

1. Cannot expand row.
2. Cannot select row.
3. Cannot edit row.

Would appreciate some advice as I have recently been advised that my application has to support IE8. Is it worthwhile trying an older version of the Responsive plugin?

Thanks
Scott

allan

Hi Scott,

I'm afraid I don't have an immediate answer for you here. The Responsive examples work no problem in IE8, but that one combined with Select and Editor doesn't. I suspect its a conflict between the selectors for Responsive and Select, but I'm not sure what.

I'll need to get back to you on that one.

Allan

dataagility

Hi Allan

Yes, I agree regarding conflict between Select and Responsive.

When IE8 runs _detailsInit() this.s.dt is empty.

Moving Select init above Responsive init and changing selectors is a hack to get it working somewhat but this is not going to bring resolution eg.

// $( dt.table().body() )
$(document)
    .on( 'click.dtr mousedown.dtr mouseup.dtr', selector, function (e) {

I have debugged a bit, but couldn't find a solution for the scope issue. Hopefully this can help yourself, or someone more experienced with DT.

Would love to see a resolution soon, but personally I have to move onto other tasks.

Cheers
Scott

allan

Hi Scott,

Interesting! Great to hear you have a workaround. I'll dig into this and post back - it will probably next week before I can do so now though I'm afraid.

Regards,
Allan

allan

This is proving to be an absolute rabbit warren... It appears to be related to Responsive and Buttons being used on the same page, but I haven't been able to isolate the issue yet. I'll need to come back to it - hopefully tomorrow.

Allan

dataagility

Thanks for the update Allen.
I've a bespoke solution currently working for my current project. I think I'll have to leave it in place considering the timeline. So, considering it's IE8 I wouldn't prioritise it to highly.