Bug 126934 - [validation] HTML 4.01 Traditional validator does not follow doctype
Summary: [validation] HTML 4.01 Traditional validator does not follow doctype
Status: NEW
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.html (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P2 enhancement (vote)
Target Milestone: ---   Edit
Assignee: wst.html CLA
QA Contact: Nick Sandonato CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-02-08 11:50 EST by Adam Archer CLA
Modified: 2013-06-19 11:14 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Archer CLA 2006-02-08 11:50:59 EST
The HTML 4.01 Traditional validator does not report all the errors that it should. It reports some but omits many. The validator should follow the doctype specification like any other validator.
Comment 1 David Williams CLA 2006-02-09 01:36:20 EST
Thanks Adam. I think you are right, can you please clarify? 

It's probably so obvious to you ... :) but can you show a few sample inputs and spell out a few of the of the missed validations? 

It will probably also be important to name exactly which version of WTP you are using. 
Comment 2 David Williams CLA 2006-02-16 03:37:10 EST
I've learned a little more about this, and the fundamental point is that our HTML validation warnings/errors do not match (exactly) things like the w3c HTML validator. (for example, if an HTML document does not have any doctype, we do not flag it as a warning). 

So, fundamentally, it would be great if there was some "tie in" between the editor (or web project) and various web-based validation services, such as w3c. 

I'm not sure if this is possible (or, if we'll just have to make some incremental improvement on our own validators) but will mark as 'help wanted' as seems a good area for someone from the community to make a contribution. 

Comment 3 Ian Tewksbury CLA 2010-04-05 14:07:06 EDT
There are many validation issues out there with many bugs and enhancements open for them.  While it would be great to just fix the validator so it matched something like the w3c I think this enhancement is just to big for its own good. 

Like comment #1 asked, if there were some specific examples to tackle that would be great but a request to "fix validation" is just not something that is very useful.  Vote to resolve unless someone would like to specify exactly what they want changed.