Re: Null values changed to "value"?

• From: Gary L Peskin <garyp@firstech.com>
• Date: Tue, 06 Feb 2001 15:37:13 -0800
• To: Russell Gold <russgold@acm.org>
• CC: html-tidy@w3.org
• Message-ID: <3A808AA9.35AEF9F0@firstech.com>

Russell Gold wrote:
> 
> As of R6, I notice that the tag:
> 
> <input type=string name=something value=>
> 
> is now treated as though it said:
> 
> <input type=string name=something value="value">
> 
> which seems odd, to say the least. Is this related to the "bug-fix" described as
> "Fixed a bug where createElement() was not properly setting Node.tag if the tag to be added could not be found in the the TagTable. A generic entry is now used instead of leaving the entry set to null."?
> 
> I would have thought that treating it as an empty string
> 
> <input type=string name=something value="">
> 
> would have been a safer choice.

This should not have changed from that bug fix since "input" should have
been found in TagTable all along.  Can you provide the actual HTML page
along with your configuration file or command line options and I'll try
to reproduce the problem.

Gary

Received on Tuesday, 6 February 2001 18:37:51 UTC