There was a similar identification bug posted the other day. I posted up a possible workaround in the comments that might be of use to you, see:
https://mootools.lighthouseapp.com/projects/2706/tickets/798-ie78-incorrectly-identified-as-trident4 Cheers, SJ On Dec 4, 5:33 pm, bluff <[email protected]> wrote: > What is the problem if mootools falls down on IE6 identification then > do it the vanilla way, or have we forgotten how to do that! > > var arVersion = navigator.appVersion.split("MSIE"); > var version = parseFloat(arVersion[1]); > > if (version == 6) { > IE6 stuff here > > } > > On Dec 4, 12:35 pm, samdev <[email protected]> wrote: > > > IE1? Is it typo? Maybe IE6? > > I don't think you can get IE1 from anywhere these days. > > > On Dec 4, 2009, at 4:04 AM, Robert wrote: > > > >> You are creazy. STOP DEVELOPING FOR IE6! > > > > Are You going to pay me for this? > > > How much? ;) > > > > But seriously - if I'm preparing intranet application for company that > > > uses IE1, I develop for IE1 or I don't GET THIS JOB. > > > It is that simple. > > > > thanks, > > > Robert
