I'm playing with using two separate divs that alternate back and forth in visibility (one covering the other). Each of these divs have a datatable in them. The table itself is being used for radically different uses each time (the two divs alternate to smooth page flipping animations).
I placed the bDestroy flag to true whenever I render the div. But I did notice in Chrome the browser detect seems to be failing but only after bDestroy. I can see the outcome from the style attribute on the table getting a "width: 100px".
Looking at the code, line 4921 of the uncompressed has some sort of browser detection because of some IE issues with 100%. Although it appears the oSettings.oBrowser.bScrollOversize is coming through as true before and after the bDestroy.
Is anyone else seeing this situation? Is there a better and absolute way of destroying the table?
I placed the bDestroy flag to true whenever I render the div. But I did notice in Chrome the browser detect seems to be failing but only after bDestroy. I can see the outcome from the style attribute on the table getting a "width: 100px".
Looking at the code, line 4921 of the uncompressed has some sort of browser detection because of some IE issues with 100%. Although it appears the oSettings.oBrowser.bScrollOversize is coming through as true before and after the bDestroy.
Is anyone else seeing this situation? Is there a better and absolute way of destroying the table?