Browser reading nonexistent code

[Hillary Handwerger]

Did you try hitting the reload button?  If your system is set to never 
look beyond what it has in cache, it won't get to your changes.

Check in Netscape, under Options, then under Preferences. Then check 
under Cache.  If Verify Documents is set at never, the system will 
always assume the one it had originally is the one to use, so won't look 
for a newer version.  Change Verify Document to Once per session. 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Hillary Handwerger
hillaryh at sme.org
Society of Manufacturing Engineers-- CoNDUIT Project
313 271-1500 ext 573 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


On Mon, 3 Jun 1996, Claudia Rebaza wrote:

> Has anyone else had a problem with their browser insisting on reading a 
> coding error that has long since been corrected?  Last week I typed an 
> "a" instead of an "i" in </i> and the browser (Netscape) continues to 
> show the </a> in the document source even though this was corrected four 
> days ago.  A colleague here has run into the same problem before but we 
> don't know what causes it or how it can be corrected.  This error shows 
> up in more than one machine.
> 
> I've also sometimes had a problem where sections of the document source 
> blink, and the affected text does not show up on the browser.  The only 
> way I've been able to fix this in the past is by erasing the affected 
> codes and text and retyping them (sometimes more than once).  Since this 
> blinking may extend to a whole paragraph of source, I'd prefer not to 
> keep doing that :>
> 
> Does anyone know why this may be happening?
> -----------------------------------------------------------------------------
>                                 Claudia Rebaza
>                        Cook Library Reference Department
> 		 University of Southern Mississippi, Hattiesburg
>      crebaza at ocean.st.usm.edu & http://ocean.st.usm.edu/~crebaza/index.html
> 
>