Re: Fwd: [webkit-dev] Removing deprecatedFrameEncoding

On 2012-01-18 10:06, Julian Reschke wrote:
> On 2012-01-18 03:48, Brian Smith wrote:
>> Please see *webkit* (not our bugzilla) bug 67882.
>>
>> What is our current situation regarding this (mis)feature? It is very
>> unclear to me. What exactly do we support regarding internationalized
>> filenames in Content-Disposition, and how does document encoding or
>> other things affect that processing? Bug numbers?
>
> Tests at <http://greenbytes.de/tech/tc2231/>.
>
> Meta bug: <https://bugzilla.mozilla.org/show_bug.cgi?id=609667>
>
> Firefox supports:
>
> - RFC 2231/5987 encoding (good)
> - RFC 2047 encoding (a bug, but hard to remove)
> - ISO-8859-1 (ok, but sniffed as UTF-8 when the octets smell like that)
>
> I believe there's also code similar to the one discussed in Webkit that
> uses out-of-band charset information, but I haven't yet test cases for
> that (needs work in my test scripts), and I don't believe we have a bug
> for that.

OK, a quick test is here:

   http://greenbytes.de/tech/tc2231/greek.asis#attwithisofnplain

See also

   https://bugs.webkit.org/show_bug.cgi?id=67882#c32

Maybe I'm doing something wrong but it appears that *only* Firefox uses 
the charset from the referring page. (If that's the case we should open 
a ticket and add it to the TODO list for Content-Disposition).

Best regards, Julian