Package: elinks Version: 0.13.2-1+b1 Tags: upstream, patch Severity: grave ELinks is not recognizing MIME type text/xml+xhtml nor text/xml, which are the recommended types for XHTML, on added file extensions. This means that, despite XHTML 1.0 and XHTML 1.1 documents are valid HTML 4 they are not recognized unless you use text/html type.
I haven't been able to test through HTTP yet, though. Severity is assuming the bug happens also on network, so lower to important if it isn't the case. The solution depends on whether the problem is just a file handling issue or general, but it's trivial in both cases: - If it's a file handling issue (it works on HTTP) it's just a matter of finding out why only text/html is accepted in the case of files. I'm sure it is straightforward, and can volunteer for a patch in this case. - If it's general all necessary is accepting both types and assuming they are valid HTML. Parts of XHTML 2 might not display correctly yet, but this has ever happened with all newer versions of HTML on legacy browsers, and is not a problem until it gets supported. I have no doubt XHTML 1 is fully supported, though, and has ever been, except for this MIME type issue.
