Re:Store.js - cross browser local storage without using cook...
by cheald on Monday June 28, 2010 @03:16PM
(#1469065)
Give IETester a whirl. IE 5.5, 6, 7, 8, and 9 preview render engines in a single executable.
Re:Store.js - cross browser local storage without using cook...
by marcuswestin on Monday June 28, 2010 @03:24PM
(#1469100)
I'm not convinced that IETester changes the underlying APIs correctly. Because of bad experience with "Multiple IE" simulators in the past I don't test on anything but the real install.
Re:Store.js - cross browser local storage without using cook...
by cheald on Monday June 28, 2010 @03:33PM
(#1469137)
I hear you there. I just wish it were easier to have multiple versions of IE laying around without having to boot a VM for each. Heh.
Re:Store.js - cross browser local storage without using cook...
by scommab on Monday June 28, 2010 @04:46PM
(#1469406)
ThinApp [http://en.wikipedia.org/wiki/VMware_ThinApp] is pretty useful when needing to do "classic" browser testing.
Re:Store.js - cross browser local storage without using cook...
by TeHCrAzY on Monday June 28, 2010 @10:20PM
(#1470161)
I don't think many people would be willing to invest $6,000 USD (minimum!) to test old versions of IE.
Re:Store.js - cross browser local storage without using cook...
by eli on Monday June 28, 2010 @04:28PM
(#1469347)
Yeah, I had trouble with those "portable IE6" implementations too. But IETester seems to be a lot closer to the real thing, at least as far as I can tell.
Re:Store.js - cross browser local storage without using cook...
by jfrabaute on Tuesday June 29, 2010 @08:54AM
(#1471200)
Hi,
IETester hooking is not perfect yet, but the engine is the correct versioned engine used on each tab. You can find more information here :
http://www.my-debugbar.com/wiki/IETester/HowDoesItWork
Regards.
Re:Store.js - cross browser local storage without using cook...
by nitrogen on Tuesday June 29, 2010 @12:52AM
(#1470432)
IEs4Linux might work for you then. It can install the original IE6, IE5.5, and IE5 under Wine. IIRC it uses a separate wine tree for each version, so there's no chance of the IE6 js interpreter being run in IE5.
I don't have access to IE5.5, would love to have someone test it.