[Hunter S]

Howdy folks,

Having tried to use the print button on some websites (in order to have a print-friendly result) after changing the ad-blocking setting, I am still having trouble getting a proper print. I have doubts about it being my ad-blocking setting anyway because the problem is happening on sites at which have printed successfully before.

I suspect that this has something to do with the latest Apple system update, one that I downloaded quite recently. The notes mentioned a change to java 'something' but I do not remember any details.

No matter what the cause I don't have, but really need, a solution.
Would appreciate any help or suggestions.

Thank you,
Hunter
G3 iBook, 10.4.8, 640 RAM

[Forrest]

Got example?

[Hunter S]

Hi Forrest and anyone else who can help,

I'm not sure this will help. But...

When I'm doing my internet banking, I need to be able to use the print button because printing (or saving as a PDF) the resulting page/doc gives me everything on the page. When that doesn't work (nothing happens), I have to command-P, then print or save as PDF. And then I only get what is visible on the screen. I am using this to save or print my receipts for all the transactions in that particular session of banking. In the not too distant past I could use the site's print button in order to get a printer-friendly page that would print (or save) in its entirety.

I'm not sure what else to say, except that when the pointer is over the button the following comes up at the bottom of the page: java:self.print().

Thanks,
Hunter

[JKT]

It is a javascript issue - some others have reported problems with Print buttons on pages (they typically use javascript for their output). If it works in the current official release of Safari, then there has been a regression in the Javascript engine since that release that needs to be or has been fixed in WebKit. Potentially it should work when OmniWeb upgrades to an even newer version of WebKit than the one it is using with the 5.6 release (assuming they manage to do so). In the meantime, you could test to see if it is due to the version of WebKit being used and if it is corrected in a more recent nightly build.

N.B. send a bug report to OmniGroup using the Send Feedback option from the help menu so that they are made aware of your problem.

[Hunter S]

JKT,

Don't know why I didn't test with Safari before. Obvious thing to do. With Safari, the button does work; so at least I have a back up until it works with OmniWeb.

Thank you for helping.