IE11 does not identify itself as IE (Prototype.Browser.IE is false) about prototype HOT 5 OPEN

Niko Wolf
January 22nd, 2014 @ 04:07 PM

Here's my quick fix (goal was to avoid changing the original prototype.js).
Include the following after prototype has loaded:

Prototype.Browser = (function(res) {
    var ua = navigator.userAgent;

    if(ua.include('Trident')){
        res.Gecko = false;
        res.IE = true;
    }
    return res;
})(Prototype.Browser);

from prototype.

Completely on the fence as to whether I should even bother to fix this. All the tests pass in IE 11, so the fact that we might think it's Firefox certainly isn't hurting us at all.

from prototype.

I think the importance of this issue depends on whether this flag is meant to be internal to PrototypeJS, or public for PrototypeJS-using applications to use. I just tried to use this flag in my application, and had to add in jwestbrook's additional test for IE 11. The documentation at http://api.prototypejs.org/Prototype/Browser/ makes it look like the IE flag is meant to be public.

from prototype.

Yeah, I wanted this to let me detect IE but it didn't, reliably. I got Gecko on IE12/Win10.

There's also Edge to consider, which is detected as WebKit.

from prototype.

These flags are used internally to replace normal code with work-arounds, so you don't try to do something on Firefox that you need to do on IE 9, since that might cause Firefox to stop working. If IE 11 passes all the tests, then the only reason to test for IE is if you want to know for some reason, not because ordinary Prototype standard code won't work in that browser, and something needs to be worked around.

Walter

On Nov 10, 2015, at 7:46 AM, GreenReaper [email protected] wrote:

Yeah, I wanted this to let me detect IE but it didn't, reliably. I got Gecko on IE12/Win10.

There's also Edge to consider, which is detected as WebKit.

�
Reply to this email directly or view it on GitHub.

from prototype.