This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
Working on this, in the context of multiparser work.
*** Bug 2510 has been marked as a duplicate of this bug. ***
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.
Still unsure about proper handling of this question, moving target to "the future", to be revisited.