This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This was was cloned from bug 17304 as part of operation convergence. Originally filed: 2012-06-04 13:13:00 +0000 Original reporter: Julian Reschke <julian.reschke@gmx.de> ================================================================================ #0 Julian Reschke 2012-06-04 13:13:54 +0000 -------------------------------------------------------------------------------- Section 5.6.4, "Page load processing model for text files", currently requires UAs to re-use the <plaintext> handler to handle content of type text/plain. This makes it impossible (*) to improve handling of text/plain, such as for: - handling format=flowed (RFC 3676), - handling FF characters for printing (see <https://bugzilla.mozilla.org/show_bug.cgi?id=92250>), and - handling text/plain fragment identifiers (RFC 5147). I believe the spec should allow the UA to augment the document with markup as long as the displayed text is not affected. (*) Unless the improvement could be done using CSS, which doesn't seem to be the case for the examples mentioned above. ================================================================================
UAs can layer any rendering they want on top (e.g. using a technology like XBL), the point is that the DOM must be as specced. This is required for compat reasons.