[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev question about embedded javascript
From: |
dickey |
Subject: |
Re: lynx-dev question about embedded javascript |
Date: |
Thu, 7 Jan 1999 05:29:15 -0500 (EST) |
> >
> > Well, if "HTML was never intended to contain text which should not be
> > rendered", why the specs for HTML 2.0, 3.0 and 4.0 say
but back to my original question: the JavaScript's newlines mean something
(they act as statement delimiters). It would be reasonable to render
<server> ... </server> like <pre> ... </pre> unless Lynx had some reason
to do something different (since it displays it anyway).
> By text not to be rendered I didn't mean comments, I meant text outside
> of any <...>. It is the fact that comments are not rendered that is
> used as a hack to protect inline Javascript from rendering (although
> a Javascript aware browser will not recognize HTML/SGML comments but
> will pass the <-- to the Javascript parser).
--
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey
- Re: lynx-dev question about embedded javascript, (continued)
Re: lynx-dev question about embedded javascript, Ismael Cordeiro, 1999/01/02
Re: lynx-dev question about embedded javascript, David Woolley, 1999/01/03
Re: lynx-dev question about embedded javascript, dickey, 1999/01/02
Re: lynx-dev question about embedded javascript, dickey, 1999/01/03
Re: lynx-dev question about embedded javascript,
dickey <=