At the moment there's too much going on to start debugging for IE(7). I mean I don't get any errors when opening the site but the layout is kinda messed up and some fx don't work as they should (compared to FF for example). Starting with individual blocks of html and the css I would try and fix the layout first getting it as close to the design first (eg. the line height in the navigation blocks at the top). I'd also test stuff (animations etc. if the line up correctly...) bit by bit and not a whole "finished" site.. too much stuff the IE can break on.
As far as debugging.. I really don't have the best answer for you as I've been dealing with it as well. I have tried the script debugger from MS and also Visual Studio (google for js debug IE7 and you'll find relevant links about this, like http://www.jarrodgoddard.com/web-development/internet-explorer-7-javascript-debugging) I think with those tools you can get the most out of it. Firebug Lite and all those bars are just not useful IMHO. jslint.com for checking your js code is helpful too. If you're js code is good there's not really much that can go wrong except for layout quirks (eg. with animations). On May 10, 3:14 pm, hamburger <[email protected]> wrote: > Hello, > I know this is not mootools related, but I'am sure that all > professionals here are using one or more good debugger. > > I have got a problem with my > page:http://www.opteynde.com/test/contest/index_7.html > > I'am using firefox and firebug to develop it. There, the side looks > fine without any bugs. > > But in IE7 .... > > My main problem is to find the bugs IE is complaining. > > For debugging I found the DebugBar v5.1. But used to firebug it seems > very bad. > > Is there any other solution simular to firebug in the world? (I'am > still on windows) > > thanks for your opinion in advance
