Most of us still have to develop stuff for IE5.5+. Let's don't go there.
On 29 Nov 2009, at 20:05, stratboy wrote: > You are creazy. STOP DEVELOPING FOR IE6!!!!!!!!!!!!!!!!!!! > > On 29 Nov, 18:46, Robert <[email protected]> wrote: >> Yes, these are two separate W2k3 VirtualPC machines. >> Do You think virtualisation could be the problem? >> >> thanks, >> R >> >> On 29 Lis, 18:32, Oskar Krawczyk <[email protected]> wrote: >> >>> Let us be clear, are you using both IE's natively, on two separate >>> (virtual) machines? Otherwise the engine detection may fail– return the >>> engine version of the natively installed iE. >> >>> On 29 Nov 2009, at 16:47, Robert wrote: >> >>>> Hmm, >>>> PHP? Are we still talking about Internet Explorer? >> >>>> IE6 identifies as: >>>> Browser.Engine.name === 'trident' >>>> Browser.Engine.version === 5 >>>> Browser.Engine.trident5 >> >>>> same as IE7 >>>> so I cant tell it is IE6 or IE7... >> >>>> thanks, >>>> Robert >> >>>> On 29 Lis, 15:42, Davor Ilic <[email protected]> wrote: >>>>> just use therfore PHP it´s easy to provide it and use it >> >>>>> 2009/11/29 Oskar Krawczyk <[email protected]> >> >>>>>> It'll not correctly with standalone versions of IE. >> >>>>>> On 29 Nov 2009, at 13:32, Robert wrote: >> >>>>>>> Mootools IE version checking not working properly for IE6. >>>>>>> Can't tell where the problem is, but it returns same result as IE7. >>>>>>> Both browsers have IE developer toolbar instaled and all MS updates... >> >>>>>>> Have You ever met this problem? >> >>>>>>> thanks, >>>>>>> Robert
