This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6299 - Show 'Parse Mode' and 'Content-Type' information by default
Summary: Show 'Parse Mode' and 'Content-Type' information by default
Status: CLOSED WORKSFORME
Alias: None
Product: Validator
Classification: Unclassified
Component: Website (show other bugs)
Version: HEAD
Hardware: PC Windows XP
: P2 enhancement
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-10 16:33 UTC by Simon Pieters
Modified: 2010-02-11 09:06 UTC (History)
1 user (show)

See Also:


Attachments

Description Simon Pieters 2008-12-10 16:33:54 UTC
From Bug 6296.

Please show the 'Parse Mode' and 'Content-Type' information by default (i.e. without having to enter &debug=1 in the URL).
Comment 1 Simon Pieters 2009-01-05 08:44:24 UTC
Given how things turned out with the v.nu integration, 'parse mode' is probably less intresting. But content-type is still interesting.
Comment 2 Olivier Thereaux 2009-01-05 15:52:12 UTC
(In reply to comment #0)
> From Bug 6296.
> 
> Please show the 'Parse Mode' and 'Content-Type' information by default (i.e.
> without having to enter &debug=1 in the URL).

The "verbose output" option, available in the UI, does this already. I don't think that info would be useful for a majority of users, so keeping it behind a "verbose" output seems appropriate.

http://validator.w3.org/check?uri=http%3A%2F%2Fwww.w3.org%2F&verbose=1

One thing we can do though, is to rename "verbose" to something that makes more sense to people?
Comment 3 Simon Pieters 2009-01-05 16:10:34 UTC
It's the only thing available to be able to tell apart HTML5 and XHTML5. Although maybe you should say "This is valid XHTML5" instead when that's what you mean. :-)

Also, it's useful to know "this is valid XHTML 1.0 but browsers will treat it as HTML" vs "this is valid XHTML 1.0 and browsers will treat it as XML", but maybe you could say so directly instead of saying so in a content-type label that the majority doesn't understand.