Seen in version: 14.2.20142.2140
Not in version: 15.1.20151.1005
Browsers tested: latest versions of IE, FireFox and Chrome.
Behaviour
However, if you first do a manual resizing of any of the column widths then you can successfully move columns.
Unfortunately we are not in a position to move immediately to the latest version, so if someone could suggest what is happening or how I could go about debugging this, I would appreciate it.
Regards
Aidan
Hello Aidan,
I tested Column Moving feature with v14.2.2140 and it behaves correctly. I'm attaching the sample that I used to experiment with for your reference. Please test it on your side and feel free to modify it in order to reproduce the issue, then send it back to me. Waiting for your response.
Regards,Tsanna
Hi Tsanna,
Thanks for the code snippet.
I would have expected any experimental focused code snippet to work, I do not think the grid is fundamentally broken, but rather there is some interplay in our codebase with 14.2 that is causing this issue. I mentioned it working in the latest version, so that it might help surface something.
I was hoping for some insight to help fasttrack the debugging process. In lieu of suggestions my approach will have to be the systematic but time consuming removal of features.
I have taken your datasource and column definitions and slotted them in place and the issue still occurs, which at least removes data and column definition from the equation.
I have narrowed this down to displaying the grid within angularUI 0.13 <tab>.
If I remove the <tab> infrastructure the drag movement is correct within the grid, if I wrap the grid within tabs it breaks.
I have been unable to make it break within your testharness, so whatever interplay is going on isn't just as simple as the presence of <tab>.
However while doing this I noticed that we are on 14.2.20142.2140 but there is a later service release 14.2.20142.2477 so I tried using that and the dragging now works as expected.
Would it be possible to get someone to have a look at what has changed in the columning moving code between .2140 and .2477 as I would like to have a clear idea of what is causing this. When broken, only listeners for the DragStart and DragEnd events are being executed, Moving, Moved and Cancelled listeners are not executed.
It seems that when your grid is placed within a tab and in case that the tab is not active the grid is initialized in a container, which is not visible. Therefore the initial caching of column size and position is not correct, which causes the problem with the not working column moving. If you have any further questions, feel free to contact me.
Regards,
Tsanna
Not sure I understand, because I believe in order for the tab contents to be visible, the tab needs to be active. And when the tab becomes active it is then that the contents i.e. the grid is created.
Also, this was working in 14.x (not sure when it broke), but we know it is broken in 14.2.20142.2140 but works in 14.2.20142.2477 and 15.1.20151.1005 without any code change on our behalf.
Is this is something that was addressed in .2477 and we can expect it to work going forward.
Hi Aidan,
After further research I found out that there was similar development issue logged in our internal system, however it's already fixed and available in the latest service release of v14.2 and later.
Thanks for that.
Feel free to close this ticket.