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


           Summary: plain text processing breaks text/plain; format=flowed
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://dev.w3.org/html5/spec/Overview.html#read-text
        OS/Version: Windows NT
            Status: NEW
          Keywords: NE
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: julian.reschke@gmx.de
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,


"When a plain text document is to be loaded in a browsing context, the user
agent should queue a task to create a Document object, mark it as being an HTML
document, create an HTML parser, associate it with the document, act as if the
tokenizer had emitted a start tag token with the tag name "pre" followed by a
single U+000A LINE FEED (LF) character, and switch the HTML parser's tokenizer
to the PLAINTEXT state. Each task that the networking task source places on the
task queue while the fetching algorithm runs must then fill the parser's input
stream with the fetched bytes and cause the HTML parser to perform the
appropriate processing of the input stream."

Handling text/plain this way seems to make it impossible to handle
format=flowed properly (unless I'm missing something about <pre>).

Oddly enough, the next paragraph does mention format=flowed (which is what RFC
2646 defines):

"The rules for how to convert the bytes of the plain text document into actual
characters are defined in RFC 2046, RFC 2646, and subsequent versions thereof.
[RFC2046] [RFC2646]"

I assume that RFC2646 is mentioned here by mistake.

That being said, it would be cool if HTML5 *allowed* UAs to do the right thing
with format=flowed.

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 Friday, 1 October 2010 13:57:59 UTC