W3C home > Mailing lists > Public > www-validator-cvs@w3.org > November 2007

[Bug 5240] fails by URI passes by direct input

From: <bugzilla@wiggum.w3.org>
Date: Thu, 01 Nov 2007 17:17:46 +0000
CC:
To: www-validator-cvs@w3.org
Message-Id: <E1Indfu-0007wx-4X@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5240


ot@w3.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |INVALID




------- Comment #3 from ot@w3.org  2007-11-01 17:17 -------
(In reply to comment #2)
> I don't think this is an ASP.net bug per say.

Call it a broken feature if you like:
http://msdn2.microsoft.com/en-us/library/exc57y7e.aspx

This is a FAQ, bill. Dozens of ASP.net coders before you have hit this issue,
and fixed their engine to produce valid markup, even when sent to the
validator. I trust you can do the same.

> However, if the markup produced by it is valid XHTML (it is) it should
> validate in your tool. Just because your tool is not recognized by ASP.net does
> not mean the markup produced by it is invaild. You are validating markup, not
> frameworks.

You are contradicting yourself. Indeed, the validator just validates markup. If
given invalid markup, it will mark it as invalid, without any consideration of
markup. The fact that asp.net (or any other tool) sends invalid markup is not
the validator's problem.
Received on Thursday, 1 November 2007 17:17:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:54:59 GMT