Debugging and Testing Websites with MozillaTuesday April 8th, 2003foopy writes: "Henrik Gemal wrote a great article on debugging your web site using Mozilla." In fact, that is something I would like to see on mozilla.org ... I fear that many people are looking for this or other information to be found on gemal.dk and similar sites at the mozilla.org site without luck. Wouldn't it be good to at least have a Mozilla-approved list of key sites likes this maintained at mozilla.org? Of course the site to be on top of that page would have to be mozillazine.org (is it anywhere mentioned on mozilla.org?) Yes, I think that Mozillazine.org is mentioned. For instance, when Mozillazine.org was having its drive for donations, I think that was put on the main mozilla.org page. Does http://directory.mozilla.org/Computers/Software/Internet/Clients/WWW/Browsers/Mozilla/ count? (on directory.mozilla.org aka dmoz.org) It would be very nice and helpful after split Mozilla into separate browser, email client, composer, calendar, etc. present installation options including not only these well known components but also various add-ons with many (or all) pieces like speellchecker, HTTP Headers console, etc... probably grouped into packs (Web developer pack, Advanced pack, ...). This is an interesting suggestion. Of late there has been a lot of hoopla over *enterprise* level products , and making Moz something like that is possible. It does have what it takes to be an enterprise level software, well , almost. There are inherent problems with Mozilla too, but seperating the different components, can help create a leaner mozilla. I guess the mozilla guys can think about this. I hope Mozilla have more web developing friendly environment. Please add line number ti voew source. A litte improvment, a great help. Please vote for bug 8589 and 15364. It's harder to do than it first appears unfortunatly :( I agree with the writer about the javascript console who say that it need some improvement. The javascript console is not too bad but not perfect for use-ability. I'm looking forward to one day that there'll be some improvment to it... I'm trying not to use the IE javascript console and use the Gecko javascript console often but unfortunately, I had failed to grasp the lack of simple displaying of the error message in the javascript console and resort to IE javascript console. It is obvious that I had failed.... What do you not like about Mozilla's js console? Where do I start? I can't easily copy just the url that points to the problem file. It does not clearly differentiate between errors belonging to different documents. Sometimes it has no scrollbars (known bug, but will anyone fix it? ;) ) That's as a user. As a developer, the consoleservice API has a lot of issues; I keep looking for time to revamp it some.... I have recently used the Dom Inspector. It was an incredible help in determining the problems I was having, both with css, and with javascript generated elements (which obviously don't show up in the view source). |