I’m working on a new design for my site, and I’ve git a bit of a roadblock with a custom gallery system I’ve written. It works fine in FF, Chrome, Safari … but IE (as always!) is being a sod!
Its almost like the ul elements isn’t going horizontal for some reason (whereas it does in FF/Chrome/Safari just fine). The weird thing though, is that it works ok on the fiddle - so I’m not sure what I’ve done differently there
IE tester on the main is 99.9% accurate for css and is likely to be better than virtual machines that have not got the correct service packs added etc. However it is very buggy and crashes all the time and there are some things it doesn’t like like file inputs and problems with transparency in some earlier versions. It does also depend on what version of IE is installed by default because IE7 emulation won’t run locally.
Nothing beats having the real version running on a real computer though
Yeah for sure. The problem is that I’m not a designer per-say … I’m a programmer I guess it couldn’t hurt to have a 2nd machine, which can boot up into different version of Windows, each with different versions of IE on - it just a PITA, as I guess it mean’s needing multiple licenses as well. I think the IE Tester one sounds good for what I need right now. As long as I can test the bulk of it, I’m sure I can do with a crash every now and then
Chrome also has an extension called IE Tab. I’ve tested some code at work on it and it seems to behave exactly like IE. Only does IE7-9 though but it’s been 100% accurate so far of what should break etc.
No you have the option of changing whatever IE version you want. My work computer has IE11 installed. I have the options of IE7-9 (they note that I need to have at least the version installed if I want to emulate it)
I don’t believe that’s true Ryan. It will only accurately emulate the current version you have installed. Any other versions will be the versions from developer tools options which are wildly inaccurate and don’t react to known bugs in those versions so is little use for testing as it’s the bugs that you usually want to fix.
I do not know how accurate yoru bug statement is, but my computer at work has browserstack which I can use (I’m the designated debugger since they know I browser Sitepoint and I like debugging ) . The IEtab emulated version compared to BStacks IE is identical. I don’t know about how accurate bugs are bug…
For example - we have a masthead slider using slick-slider (Foundation). We had an issue where it wasn’t automatically rotating in IE9 only. My IEtab correctly showed that it was broken when I selected to see it in IE9.
Also had an issue where a span was exceeding the parents width and on the masthead slider, you could see caption2 behind caption 1 (faded). BStack on IE9 showed this. The emulated IEtab also showed this.
Bugs aside, seems accurate for me. Perhaps showcasing bugs are the downfall.
IE8 has a bug and fixed positioned elements using :after scroll with the document when they shouldn’t. IE9+ apply it correctly but not in IE8. The developer tools in IE get this wrong and so will your IE tab I believe (unless you are running a native IE8).
The developer tools are OK for simple stuff but just can’t be relied upon enough to debug properly.