IE's have many issues. Which one you mean by the MIME type one?
Btw, it's a standard way of obtaining an xmlhttprequest object, cross
browser. If the user uses IE6, it's his problem imo.
sashee
On Sat, Apr 25, 2009 at 9:18 PM, Matthew Toseland
<toad at amphibian.dyndns.org> wrote:
> On Friday 24 April 2009 01:05:35 Daniel Cheng wrote:
>> 2009/4/24 ?<sashee at freenetproject.org>:
>> > Author: sashee
>> > Date: 2009-04-23 20:06:00 +0000 (Thu, 23 Apr 2009)
>> > New Revision: 27271
>> >
>> > Added:
>> > ? trunk/freenet/src/freenet/clients/http/staticfiles/js/
>> > ? trunk/freenet/src/freenet/clients/http/staticfiles/js/progresspage.js
>> > Modified:
>> > ? trunk/freenet/src/freenet/clients/http/FProxyToadlet.java
>> > ? trunk/freenet/src/freenet/clients/http/ToadletContainer.java
>> > ? trunk/freenet/src/freenet/clients/http/ToadletContextImpl.java
>> > Log:
>> > The progress page is now refreshed with AJAX, if enabled in the
> configuration and in the browser.
>> >
>> > Modified: trunk/freenet/src/freenet/clients/http/FProxyToadlet.java
>> > ===================================================================
>> > --- trunk/freenet/src/freenet/clients/http/FProxyToadlet.java ? 2009-04-23
> 20:04:56 UTC (rev 27270)
>> > +++ trunk/freenet/src/freenet/clients/http/FProxyToadlet.java ? 2009-04-23
> 20:06:00 UTC (rev 27271)
> ...
>> > +
>> > +function loadXMLDoc(url) {
>> > + ? ? ? req = false;
>> > + ? ? ? if (window.XMLHttpRequest && !(window.ActiveXObject)) {
>> > + ? ? ? ? ? ? ? try {
>> > + ? ? ? ? ? ? ? ? ? ? ? req = new XMLHttpRequest();
>> > + ? ? ? ? ? ? ? } catch (e) {
>> > + ? ? ? ? ? ? ? ? ? ? ? req = false;
>> > + ? ? ? ? ? ? ? }
>> > + ? ? ? } else if (window.ActiveXObject) {
>> > + ? ? ? ? ? ? ? try {
>> > + ? ? ? ? ? ? ? ? ? ? ? req = new ActiveXObject("Msxml2.XMLHTTP");
>>
>> arugggh!!
>> If I were you, I wouldn't support IE6/earlier.
>> Not only this is ugly, IE6/earlier have way too many security issue..
>>
>> XMLHttpRequest have been aviliable since IE7.
>
> Even IE7 has MIME type issues, no? Although those can be worked around by
> changing a registry key or converting text/plain to text/html in a <pre> just
> for IE???
>
