Block dragging not working in IE10

Dragging blocks from the block menu, or dragging them on a page to reorder them does not work in IE10.

I'm experiencing this issue on, and I also tested this on a fresh install of - where the issue still occurs.

From what I can gather, the CSS property transform: matrix() is being used to move the draggable box, but it doesn't update any of the position values as you attempt to move it. It just hangs on the position where you first grabbed it.

The client my website is for is a stuck with using IE10, so simply upgrading to a modern browser is not an option for me, unfortunately.

View Replies:
PineCreativeLabs replied on at Permalink Reply
No one uses IE anymore, so I wouldn't bother with it. Currently, less than 5% of the internet uses IE, and this number is continuously shrinking.

Take a look at these stats:

I would show your client those stats, and convince them to switch to Chrome or Firefox.
frankdesign replied on at Permalink Reply
Well my client does. They're a large scale public sector organisation using the site for their internal purposes, so public usage stats won't change their mind. They have their own reasons for sticking to that browser.
MrKDilkington replied on at Permalink Reply
Hi frankdesign,

I can confirm that blocks cannot be dragged in IE 10. They can be dragged in IE9 and IE11 - it makes me think there is a quirk in IE 10.

I agree that usage stats won't reflect that some large organizations use Internet Explorer.

One issue is that IE 10 is now end of life, as of January 12, 2016 it stopped receiving fixes, technical support, and security updates (with exceptions for some operating systems and special support arrangements). In all honesty, I am not sure how much energy will be devoted to fixing this.

A GitHub issue was created that you can comment on:
Blocks cannot be dragged or moved in edit mode using IE10 #5379
mnakalay replied on at Permalink Reply
Concrete5 uses a third party js library for the drag and drop of blocks if I'm not mistaken:

I agree with MrK that the C5 core team is probably not going to devote much energy to fixing this kind of edge case.

Maybe the script Github repo would be a good place to ask for a solution?