Re: Browser differences within <PRE> tags...

Daniel W. Connolly (connolly@hal.com)
Fri, 01 Jul 1994 11:42:58 -0500


Message-Id: <9407011642.AA05581@ulua.hal.com>
To: glv@utdallas.edu
Cc: Multiple recipients of list <www-html@www0.cern.ch>
Subject: Re: Browser differences within <PRE> tags... 
In-Reply-To: Your message of "Fri, 01 Jul 1994 18:20:40 +0200."
             <94Jul1.095733cdt.13627@utdallas.edu> 
Date: Fri, 01 Jul 1994 11:42:58 -0500
From: "Daniel W. Connolly" <connolly@hal.com>

In message <94Jul1.095733cdt.13627@utdallas.edu>, Glenn Vanderburg writes:
>He finally solved the problem by enclosing the whole thing, <INPUT>
>tags and all, inside a PRE element.  ...
>
>The current HTML 3.0 DTD explicitly permits this, and the current HTML 2.0
>DTD (which, I am aware, does not necessarily reflect reality) explicitly
>prohibits it.

I think you're mistaken.

What evidence did you base this conclusion on? Here's some evidence
that shows that the current HTML 2.0 DTD permits this:

[Whether it should or not is open to debate... ]

connolly@ulua {** NONE **}../html-test[1037] cat test.html
<!DOCTYPE HTML PUBLIC "-//W3O//DTD WWW HTML 2.0//EN">
<title>Can INPUT go in PRE?</title>

<form action="xxx">
<pre>
Enter xxx here: <input>
</pre>
</form>

connolly@ulua {** NONE **}../html-test[1041] SGML_PATH="%N.dtd:%N.sgml" sgmls h
tml.decl test.html
(HTML
(HEAD
(TITLE
-Can INPUT go in PRE?
)TITLE
)HEAD
(BODY
AACTION CDATA xxx
AMETHOD IMPLIED
AENCTYPE IMPLIED
(FORM
AWIDTH IMPLIED
(PRE
-Enter xxx here: 
ATYPE IMPLIED
ANAME IMPLIED
AVALUE IMPLIED
ASRC IMPLIED
ACHECKED IMPLIED
ASIZE IMPLIED
AMAXLENGTH IMPLIED
AALIGN IMPLIED
(INPUT
)INPUT
)PRE
)FORM
-\n
)BODY
)HTML
C


Dan