I've peen telling people for 18 months that this is a problem!

Here's some simple code:

  var docText = "<html><head><title>Something New</title></head>
                 <body>Blah, blah, blah.</body></head>"

  // write the page
  with ( document ) {
    close();
    open( "text/html", "replace" );
    writeln( docText );
    close();
  };

For 'whatever' reason I wish to reuse the existing loaded and rendered
page for something else.

When I use this in Netscape 4.7x it works perfectly.

As I understand it Netscape generates an internal 304 invalidating
the page in cache, the memory is freed, new memory is requested and the new 
content is displayed, all without a trip to the server.

I have whole websites based on these principles!

Netscape 4.7x still runs them just fine, but Mozilla and Netscape 6.x
just go belly up over this simple feature.

Reply via email to