W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > November 2012

[Bug 19831] Investigate overrideMimeType()

From: <bugzilla@jessica.w3.org>
Date: Fri, 09 Nov 2012 12:08:38 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-19831-2532-D1T1F8F2IF@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19831

--- Comment #13 from Hallvord R. M. Steen <hallvord@opera.com> ---
> I'm not sure people are clamoring about
> what I'm talking about in my previous comment (inspect response headers
> before deciding on the mimeType to override with if any).

Well, I've never seen it done but the reason for that might of course be that
it's generally not supported at all ;-)

I'd like some implementor comments here, if possible.. The cost for
implementors may not be worth the small extra benefit.

> I'd love to just force all requests in text/plain
> and have jQuery's own internal conversion logic handle parsing...

Now, now.. usually JS authors want the browser to work harder and do more of
the heavy lifting, so be careful what you ask for ;-)

Finally, overrideMimeType() is sort of obsolete with the responseType/response
approach. The only remaining use case is to fix decoding of content with a
misleading charset in content-type. Therefore, overrideMimeType() will
hopefully be less and less used, so the details we're working on here aren't
worth a lot more of our time IMO.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 9 November 2012 12:08:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 9 November 2012 12:08:40 GMT