[Bug 10954] plain text processing breaks text/plain; format=flowed

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10954

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |FIXED

--- Comment #6 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-11 22:12:27 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: This was already implicitly supported, but I've added a note and
some more text to make it clearer that the spec is not trying to contradict
those other RFCs.


> I'm very surprised that anybody is interested in the DOM generated for text/plain

This actually turns out to be surprisingly common (enough that UAs have to be
interoperable on the handling of short text files in iframes). I highly
recommend working as QA for a browser vendor for a couple of years, it is quite
enlightening. :-)

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 11 October 2010 22:12:30 UTC