We have placed the smsx.cab file for version 7,4,0,8 on the web server and changed the reference in source code to point to the new version. I have tested the upgrade in IE8, IE10, & IE11 (it is necessary to test in all 3 because our customers from different agencies are using different versions of IE). Only IE8 works correctly in formatting. Well, it has worked fine with the 6,5,x,x version. So that is no surprise. However, both IE10 and IE11 do not format correctly after downloading the new version to the two PCs. A portion of the the text at the end of one page is spilled onto the next page, which is not supposed to happen and is not happening in IE8. The only remedy for these newer IE environments after the upgrade is to switch on the Compatibility View. The formatting will then work properly. This doesn't seem right. If the formatting needs Compatibility View to work, then what is the point of the upgrade? Is there something that we have missed? Or is this how it's suppposed to be for version 7,4,0,8?

Hi

Are you quite sure that this isn't a browser artefact?

I suggest that you set up a document that carries (via Page Setup) the same header, footer, margins etc. that you apply with ScriptX, and test that in 'vanilla' IE10 & 11 without using ScriptX.

ScriptX uses IE's print engine, so it things work in IE they should work the same in ScriptX. But if there's a problem in IE we can't 'make it better'.

I hope that this helps.

Jerry

We've been using ScriptX for print formatting for many years. We went through upgrade to IE8 with no problems. We are using the same method for IE10 & 11 as we did for IE8. The same document that is formatted correctly in IE8 (with the ScriptX version 7,4,0,8) does not format correctly in IE10 & 11. The printing is fine. But the formatting is not.

Like I said in my previous posting, the formatting problem can be corrected in IE10 & 11 after ScriptX upgrade only by setting the browse to Compatibility View. Some of our customers who are using IE10 are already setting their browsers to the Compatibility View using ScriptX version 6,5,x,x. So it seems the upgrade is not doing anything for IE10 & 11.

If it worked in IE8, how can it be an IE problem?

>> If it worked in IE8, how can it be an IE problem? <><

There are some BIG browser changes made by Microsoft after IE8. Of course some of those can cause problems, just check Google for a sample. This is exactly why they gave you compatibility view.

Like I said, your first job is to test the same content in the different browser versions *without* using ScriptX, as I describe above.

If you can't find any diferences, then that will at least confirm your suggestion that it must all be ScriptX' fault.

One more thing.

ScriptX is not a printer driver, and it doesn't usually 'touch' a document's formatting.

What are you using ScriptX to do?

I understand that ScripX is not for document formatting. We have a web application that is using ScriptX for all of its printing. The formatting is done using XSLT. All printing shares the same .xsl file for formatting. The same .xsl file is where the code referencing the newest version of smsx.cab resides. I cannot print the same documents from this web site without using ScriptX object unless I resort to print function from the web browser. But that wouldn't be comparing apples to apples because I would have to bypass the XSLT formatting. Using version 7,4,0,8 in IE 10 & 11 results in incorrect rendering of some documents. However, using the same version ScriptX on the same documents in IE8 does not have that ill effect.

Hopefully you're quite certain that IE9 & later are not treating .xml/.xsl files any differently to IE8.

In other words, you're sure that this is not a browser compatibility issue that has nothing to do with ScriptX.

If so, please send a repro (simply as possible) of the behavior you're seeing to me at feedback@meadroid.com and we will be happy to take a look. 

I have just tested in IE11 with the 7,4,0,8 version ScriptX downloaded to its hard drive. But this time I was testing from a site on a different web server where the XLST code for formatting is still pointing to the older version (6,5,439,12) ScriptX. This round of testing was done to the same document that was mentioned in my previous posting, but this time the formatting is correct. When I say correct formatting, I judge it by looking at one of the pages where all the text is supposed to fit into one page. When the formatting is messed up, the last two paragraphs will spill over to the next page. This PC does not have any previous version of ScriptX downloaded to its hard drive priort to the 7.0 version. I'm not clear exactly how ScriptX work here. The versions on the web server and on the hard drive do not match. But no error was generated. And I did not switch the browser to Compatibility View. Will you explain to how this could have worked. Does this mean IE1 does not treat my XSLT code differently from IE8? Or is there some other reason.

On the other hand, I tested in IE10 with the identical scenario as described above (two versions of ScriptX do not match), formatting was still incorrect unless I switch to Compatibility View. It behaved exactly the same as when I tested with versions of ScriptX being identical.

I'm not sure how to go about reproducing what I'm seeing. The only way I can judge if the formatting is correct or not is going through the pages one by one in Print Preview. The only way I can think of is to scan the pages and attach them to my email. Any other suggestions?

Hi

If you have (say) 7.4.0.8 installed on the test PC then whatever version is on the server doesn't matter ... the client PC won't go 'backwards, it will always use the version it has installed. You can check for that here:

http://scriptxsamples.meadroid.com/Basic/InstalledVersion/release/DOCTYPE

If you can provide a simple XSLT test file that we can run here, then that's your next step. We'll never resolve this in forum posts like this, it's too slow and protracted.

Never mind. I got both to work now. The only mystery is why IE11 worked without the .xsl formatting source code pointing to version 7.4.0.8 (both PCs have this new version installed on the hard drive), whereas IE10 only works if the source code points to the new version, which is what we would expect.

Anyway, thank you very much for your patience and willingness to help.