In the location object and also in the location bar URIs related to a 
javascript file do not execute that script in the context of the actual 
document like implemented in Netscape 4.x but does destroy the actual 
document an display the source text.

This happens independet from the Content-Type header sent by the server. 
This is not nice. If the server sends one of following Content-Type 
headers "text/javascript", "application/x-javascript", 
"text/ecmascript", "application/ecmascript" the script should be 
executed in the context of the actual document without destroying that 
existing document like known from NN4.x. If the Content-Type header is 
"text/plain", then the server expresses that this data is to be 
displayed as new plain text document, which is the behaviour Mozilla 
does allways. But this behaviour should be only, when told by the server 
using the Content-Type header "text/plain".

Greetings, Georg


Reply via email to