6299 2008-12-10 16:33:54 +0000 Show 'Parse Mode' and 'Content-Type' information by default 2010-02-11 09:06:09 +0000 1 1 1 Unclassified Validator Website HEAD PC Windows XP CLOSED WORKSFORME P2 enhancement --- 1 zcorpan dave.null ot www-validator-cvs oldest_to_newest 22733 0 zcorpan 2008-12-10 16:33:54 +0000 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). 22899 1 zcorpan 2009-01-05 08:44:24 +0000 Given how things turned out with the v.nu integration, 'parse mode' is probably less intresting. But content-type is still interesting. 22919 2 ot 2009-01-05 15:52:12 +0000 (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? 22920 3 zcorpan 2009-01-05 16:10:34 +0000 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.