in reply to Data Missing?

This is slightly off-topic, but I never understood why all browsers to realod pages when they print them. Logically the browser should already have everything it needs to print it (since it already rendered the page to the screen). What other info could hte browser possibly need to print the page that it wouldn't have already (unless the browser is poorly designed and while the page is being viewed it has already forgotten how it rendered it).
Les Howard
www.lesandchris.com
Author of Net::Syslog and Number::Spell

Replies are listed 'Best First'.
RE: Re: Data Missing?
by turnstep (Parson) on Apr 11, 2000 at 19:29 UTC

    Some do, some don't. Some even reload the page when you try to view source (!). Ideally, it should pull everything from its cache, unless the cache has been set to zero. As to why, it's just the way the browser coders decided to do it. I can't think of any obvious rational as far as printing except for the fact that it might be easier in their code to call the page then to retreive it from cache. I work on Mozilla, and this bug came up a while ago - Mozilla will be smart enough now to know when to load from cache, and when to reload the page.

    FWIW, I think the first answer that chromatic gave is the best solution (not returning a form, just an html page.

      I find it helpful to return the values as text, but use a bit 'o Javascript to fake a hyperlink on some of the returned text. (Clicking the link calls a Javascript function to Submit the value clicked. That way you can have a form submission with no Submit button, it just looks like a hyper-link.) This is useful when you are returning your results as text, but want some interactivity functionality.