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


--- Comment #3 from Julian Reschke <julian.reschke@gmx.de> 2010-10-02 14:00:11 UTC ---
(In reply to comment #2)
> What's the use case for serving format=flowed over HTTP? Wouldn't it make more

The same as sending it per email, I guess.

> sense not to put UA-removable line breaks in the text data and to make sure the
> styling of the pre allows the UA to wrap long lines?

As far as I understand, that would be a change over what's being done today.

> I worry that allowing something here without requiring it would expose a
> different DOM in different UAs.

I'm not sure how the DOM exposed for something that hasn't got any support
today is really relevant. That being said, I'd be happy if the spec required

But the original issue would remain: by being overly specific the spec in
principle prevents innovation in text/plain. It shouldn't.

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 Saturday, 2 October 2010 14:00:14 UTC