Forums

Hi All,

I'm using a scrollable datatable in our project to display a set of 100 plus records (dynamic).

The first column is a link upon clicking of which it opens up a popup (panel) which shows a lot more data.

I do the following:

1) I sort the grid using any column
2) Click on the first column to open up the panel
3) Close the panel using the close button.

Immediately I get an error in IE browser:

A script on this page is causing Internet Explorer to run slowly.

I'm using the YUI version 2.8.2r1.

I read the related tickets on this issue but none could actually fix the problem.
I have not been able to isolate the problem if it's an issue with the Panel (since I'm opening & closing the Panel with considerable amount of data) or a data table issue reported elsewhere.

When I'm closing the Panel on the hideEvent I'm destroying the panel using panel.destroy() method.

I checked the release notes of 2.8.0 where I found this:

■Enhancements
■DropdownCellEditor now supports multiple and size properties.
■Calling DataTable's destroy() method now calls Paginator destroy(), when applicable.
■Added beforeRenderEvent.
■Added clearScrollPositions() and scrollTo() to ScrollingDataTable.
■Performance improvements for ScrollingDataTable in IE.
■Bug Fixes
■Bug fixes for DataTables rendered within table markup.

I'm not sure what exactly was fixed here. But the problem is easily reproducible in almost all the places where we use a datatable.

Your help is appreciated.

The close button scenario is one of an instance where I'm getting the error message.

I do get the same error message few times when the panel is closed and I try to click on the link on the table again.

Can you tell me how is it different if I just hide the panel as you pointed out and also when I destroy the panel each time?

The content on the panel is huge, we have 2 grids bound to 2 datatables displayed in it and a lot of div bound to the data in the datatable.

On the click of the link on each row in the base page grid, wee load the xxx.html page which is loaded first, then there are 2 grids bound using the datatable and is rendered on to the divs inside the loaded html. Then we have lot of Dom elements that is being assigned on the click of a row in the grid. So it won't be possible to assign everything in an innerHTML.

Please note: When we used firefox the memory consumption is pretty less, whereas in IE it is huge. That was one of the reason that I felt it could have something to do with the memory leakage issue mentioned in the site.

Ok, thanks for your response. It was helpful.