This content has been marked as final. Show 4 replies
I've just been informed that my above solution does not solve the problem in all cases because htmldb_Get updates the report automatically when the report ID is provided as an argument to htmldb_Get();
As such I've updated my example not to provide the ID to the htmldb_Get call... and just to use the returned text a single time.
This way the data is only appended after the header and footer processing is completed. Removing the bounce.
This probably isn't the best method, and I should probably update it to use the XML mode so that it's pure DOM object manipulation, but this will do for now.
As it turns out, the modifications above only solve the problem on a sufficiently fast machine.
It should not be considered an absolute solution in any respect.
On a sufficiently complex page the report jitter/flicker will still be visible while IE updates the display.
A better solution would be to re-implement the multiple innerHTML replacements as a single innerHTML on a temporary node (which has not yet been inserted into the DOM Tree) followed purely by DOM function manipulation.
I will try to work together an example of the problem when I get some more spare time.