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

[Bug 19831] Investigate overrideMimeType()

From: <bugzilla@jessica.w3.org>
Date: Wed, 07 Nov 2012 13:08:35 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-19831-2532-725BPJYx1t@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19831

--- Comment #11 from Julian Aubourg <j@ubourg.net> ---
> D'oh - IE (8) throws because this method isn't supported in IE at all.

Hahaha ;)

> I also note that no browser currently throws the prescribed SYNTAX_ERR
> for invalid MIME types. I hope we'll get away with it compat-wise, but
> we might not.

They should :/

> Julian, I think you said the method was more used than I thought - in
> among others jQuery.

No, not quite. But we've been asked to support it on our jqXHR abstraction so I
know for a fact that our users have a need for it. That being said our
implementation puts the new mimeType in an internal option and calls the native
overrideMimeType before sending (see
https://github.com/jquery/jquery/blob/master/src/ajax/xhr.js#L78). We never had
any complain about this... so 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).

> Any idea what the most commonly used argument strings are?

No idea. I dunno if it is used to disable native XHR xml parsing or enable it
or any other reason.

> Does jQuery's AJAX logic use overrideMimeType() internally?

No, because it's not supported by all browsers we target as of today. This may
change in jQuery 2.0. I'd love to just force all requests in text/plain and
have jQuery's own internal conversion logic handle parsing... would make our
code that much simpler.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 7 November 2012 13:08:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 November 2012 13:08:43 GMT