Forums Home / Wijmo / General Discussion
Posted by: rasika-sinha on 14 September 2017, 12:05 pm EST
rasika-sinha
Posted 14 September 2017, 12:05 pm EST
Hi Team,
I have a flex grid in react and all the columns in it are links to route to some other page in the application. They work fine, but as soon as I freeze one of the columns, the frozen columns link stops working. The frozen column becomes like a readonly column. Can you please look into it and share your input.
Thanks.
rasika-sinha
Posted 14 September 2017, 12:05 pm EST
Just an update on the above issue, it is only occurring in IE. Please share your inputs.
Thanks.
manish-gupta1
Posted 14 September 2017, 12:05 pm EST
Hello Rasika,
We are sorry, we are unable to replicate the issue at our end with build 5.20171.293.
Please refer to the attached sample that depicts the same.
If issue persists, please modify the attached sample depicting your issue so that we can assist you accordingly.
Thanks,
Manish Kumar Gupta
2017/06/FlexGrid_frozenColumn.zip
rasika-sinha
Posted 14 September 2017, 12:05 pm EST
Hi Manish,
Thanks for the sample code, I am looking into it. Just for your information the issue is with IE11 only.
Thanks.
rasika-sinha
Posted 14 September 2017, 12:05 pm EST
Hi Manish,
My application is a single page application and I don’t want a location change(href) on my link click. I need to trigger a function which will perform some actions.
If I place an href in the frozen column then it works for me also, but I need an onclick event binded to the anchor/button element of the cell. Can you please let me know how to make that work in IE11 with frozen column.
Inside the itemFormatter -
let eButton = null;
eButton = document.createElement(‘button’);
eButton.innerHTML = row.dataItem.Name;
eButton.onclick = (event) => {
this.onNameClick(row.dataItem.ID, row.dataItem.Name);
};
cell.innerHTML = “”;
cell.appendChild(eButton);
Thanks
rasika-sinha
Posted 14 September 2017, 12:05 pm EST
Hi Manish,
Any update on this issue?
Thanks
manish-gupta1
Posted 14 September 2017, 12:05 pm EST
Hi Rasika,
Thank you for additional information and reporting this issue. We are able to replicate the issue at our end and it looks like a bug. Hence, this issue has been escalated to the concerned team for further investigation with tracking id 266102. We will let you know as soon as we get any information on this issue.
In the meantime, use following code snippet in initialized event:
grid._useFrozenDiv = function() { return false; };
It should work!
Thanks,
Manish Kumar Gupta
rasika-sinha
Posted 14 September 2017, 12:05 pm EST
Hi Manish,
The given code snippet works for me, thanks a lot. Because of this change, should I expect any other issues in IE?
Thanks.
manish-gupta1
Posted 14 September 2017, 12:05 pm EST
Hello Rasika,
The given code is just a workaround. We will share information with you as soon as we get any information on escalated case.
As far as I tested, there should not be raised any issue due to given code snippet. If any issue occurs due to this, please let us know.
Thanks,
Manish Kumar Gupta
jay.ferguson
Posted 16 October 2017, 5:22 pm EST
Hi Manish, we ran into this same problem in version Wijmo Library 5.20172.334
The work around
grid._useFrozenDiv = function() {
return false;
};
Allowed us to add an event listener and fire the event but it caused other frozen column display issues in I.E. so we have to work around further. Probably by adding the event listener to the frozen div. I was wondering if this specific bug has been fixed in the latest build which seems to be 5.20172.359.
Also I looked for a bug tracker to find the tracking Id you listed; tracking id 266102. But I don’t see a tracker web page for these issues. Any help would be appreciated.
Jay Ferguson
manish.gupta
Posted 20 January 2018, 8:18 am EST
Hi,
This is the expected behavior. The FlexGrid tries to improve performance in IE by adding a special fixed div to host frozen cells. These extra frozen cells are clones of the original cells, and therefore do not trigger events attached to the cells.
Turn off frozen cells by setting the (new) “cloneFrozenCells” property to false. This will disable the clones and the original cells will fire any attached events as usual. There will be a penalty in scrolling performance though. For example:
s.cloneFrozenCells = false;
~Manish
