Hi,

We are a new customer and have started using your components, first with the downloader control. However, we are having a pretty big problem with IE compatibility that I can't seem to get around:

We generate an HTML report and have a toolbar button that lets the user "download" the PDF version of the report. When the user clicks this button in the browser, we have JS code:

eo_GetObject('downloader').start();

When the user clicks the PDF button in Firefox, and Chrome, everything works great: there is a slight pause while the server creates the PDF file, and then we are prompted to download the file.

However, with IE we get a completely different experience. In that browser, when the user clicks the PDF button, a new window pops open with a URL like this:

http://www.mydomain.com/eo_web.ashx?id=
D877A66C-9E75-4d29-BD48-426B705280FD&dldp=909C64D699E4E9DAE0AB43CC5DBD53212C1150C43
3F260320F620D303439A5EAF10FB09D683010527765808D13FAB4A6D565C686BC6044EFE49A182953923
5D616876CC2A48C400B2CB4C457183F249EFBE5C61D73A9E1215EF060F1042D5FBFC3BD5356397FEDC
395AD89C7A003F5D3D35AD701AEAD3E0588DE99E502AAA6D84B4C5EA0188AED55D8046B4CAA312E4
739FB0CEB708AA43F6A7B9D86E64C6519181C513E608F3FBAE4792E63CC1A2012155460EC619A8FB985958020

however, the window just sits there. The progress bar in the window slowly goes no where, and the user is never able to download the file. After a few minutes, the window times out and no content is delivered. Additionally, even though that window is launched, it doesn't look like any server side code is actually executed. We have debug.writeline's on the server to tell us as soon as downloader.start is called, and nothing shows up when that JS is run, so something is definitely wrong here.

Any ideas?

take care,
jasen

Oh, and one additional piece of information: if i step through the Javascript in IE, very slowly, it works SOMETIMES. So it feels like some kind of timing issue.

Hi,

We are not able to reproduce the error, so we will need a test app in order to look further. The test app also helps us to ensure that we are indeed working on the same issue as yours. Otherwise we would be shooting in the dark and still get nowhere.

Thanks!

Hi,

It's our standard procedure to require reproducing app/pages when the problem is not obvious. We not only need that to see the problem, but also need it to verify whatever solution we come up will work for you. We do not do the kind of can you try this, can you try that back and forth kind of troubleshooting. That approach will waste both of us more time.

Sorry about that. We wish you the best luck in finding a working solution for you.

Thanks!