Hi,

  I am working on an application that has both browser and scriptx prints. When I first print a web page that is scriptx enabled, I am getting the print correct. Now when i make a print through browser, the print is retaining header and footer information from my previous print. I guess the values are saved in registry and not clearing out. I would be very thankful if some one could provide any information on this.

Following is my working environment:

Scriptx version - 6.5.439.72

IE version: 8 (issue happens in version 7 too)

Windows XP

Thanks,

Raju.

Hi Raju

These days the only time that a header and footer get 'stuck' is when a script has crashed or power has failed to the PC, before we have a chance to restore the user's defaults. In that case, the attributes that you have set with ScriptX beccome the user's defaults and the ony way to change thiose values is manually through IE | File menu | Page Setup.

I hope that this helps.

Hi Jerry,

   Thanks for responding me. I see the issue consistently even without pc crashing. However, I think I found a way to solve the issue. In our code scriptx security manager and factory objects are placed in a div element as inner html. we find the issue then.

Now when i placed those objects in the html page direclty not as a div element it resolved the issue.

Can you please provide any suggestions?

Thanks,

Raju

Hi Raju,

Dynamically creating the security manager and scriptx objects is not recommended.

Regards

Pete Cole
MeadCo

Hi Pete,

We have the same issue/question.  If a user opens a new tab and visits a different website, the custom header/footer/margins we set with ScriptX on our website are carried over to the new tab (different domain/website).  I have investigated using the "Allow" feature in Manage Add-Ons within IE to limit the ScriptX scope to our domain only, but have not had any success.  Is there a way to programattically change the custom headers & footers back to the browser default after a MeadCo ScriptX print has completed? 

Thanks

Hi

My post from April 7th (above) represents our general stance on this..

Please update to the current 7,2,0,36 release and re-test, and let us know your results.

Thanks.