1391 2005-05-12 00:53:56 +0000 Direct Input validation needs a "parse mode" option? 2007-04-04 04:07:21 +0000 1 1 1 Unclassified Validator check 0.7.0 All All NEW P4 minor 1.0 1 ot ot wjs6797 www-validator-cvs oldest_to_newest 3392 0 ot 2005-05-12 00:53:56 +0000 Since the Direct Input validation cannot rely on mime type to get a hint of the proper parse mode to be applied, cases when the other methods to detect the parse mode fail (e.g unknown FPI) result in a fallback to SGML mode, which is not always the proper thing to do. Perhaps an SGML/XML switch (similar in a way to what Nick is doing) would help. 14025 1 ot 2007-02-20 07:37:54 +0000 Working on this, in the context of multiparser work. 14442 2 ot 2007-03-15 04:58:45 +0000 *** Bug 2510 has been marked as a duplicate of this bug. *** 14544 3 ot 2007-03-27 05:23:12 +0000 See also http://www.w3.org/Bugs/Public/show_bug.cgi?id=24#c13 for an alternative to a parse mode option in direct input, something I am still unsure is a great idea... Quoted here: > I think in the absence of media type information, the validator should either > (1) force the user to choose one before performing validation, or (2) first > issue a warning about lack of media type information and then check if the > character stream begins with (ignoring BOM) "<?xml", and, if so, use XML mode, > otherwise SGML mode. In case of (2) the user should be able to change the mode > and revalidate. 14661 4 ot 2007-04-04 04:07:21 +0000 Still unsure about proper handling of this question, moving target to "the future", to be revisited.