Re: lynx-dev question about embedded javascript

[dickey]

> > no - the examples I know of are delimited with <server> and <script> 
> >  
> > (looks rather ugly when Lynx shows it on the screen, since JavaScript 
> > is line-oriented, and all of that is lost in rendering). 
>  
> <script> is HTML, lynx parses it right and ignores the content. 
> <server> isn't HTML, lynx doesn't know anything about this tag so 
> it ignores it, and shows the content (according to whatever mode 
> is in effect). 

most of the files I've seen use <server>.  The text enclosed is JavaScript,
which pays attention to newlines: someone decided to make ';' optional
syntax for most occurrences.  So running the text together is misleading.
(Of course, if lynx interpreted JavaScript, then it wouldn't display it ;-)
  
> I assume the content of <server> is meant to be interpreted by a server, 
> so a file with that tag in it isn't meant to be viewed by a HTML browser 
> without preprocessing.  So no wonder you don't like how lynx shows it. :) 
>  
> I guess other browsers would have the same "problem". 
I didn't look with IE - this may be NS-specific stuff.
  
> Do you want to add recognition of <server> to lynx, to be able to view 
> the code verbatim?  It might make sence for some people, but isn't really 
> text/html. 

I agree - but there's cases like that where Lynx accommodates things that
aren't standard.

A similar (unrelated) issue: I've seen NS interpret text with backspaces
as underlined/overstruck.  Likewise html doesn't do anything useful with
backspace, but it would make Lynx more useful (perhaps).
  
>    Klaus 
> 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey