You are quite right. JS errors are much more of a problem in IE than they are in Firefox. In FF you pretty much see the errors when:
a) You are running Firebug or any other error console b) When things don't work as they should In IE (6, 7 or 8) JS errors pretty much show up every time. Most of the time by things not working but all the time by the silly yellow icon in the left bottom of the browser. The problem I have with that is that even if everything is working on the site it simply looks bad. But when I trace the errors most of the times they are in files I simply cannot change or edit and certainly not eliminate. I do a lot of work in Joomla and it seems that even stock Joomla installations have some pretty nasty errors due to Motools / jQuery interaction. If I add even the most innocuous third party add on then it's error city in IE. For instance, I have a site sporting the usual Joomla suspect, plus the JCE Editor (indispensable), a Superfish menu (again, necessary because the client is bent on a vertical hierarchical menu with background images) and an image rotator in the header (again another client requirement). Everything works but there are some "Null is not an object" and other annoying errors, but the site works. The other day the client requested an accordion feature and I tried probably 5 to 8 different script: Prototype, JQuery, Mootools, you name it. All worked fine in Firefox (with a tremendous number of errors in firebug) but they all blew up in IE. My frustration is that I honestly have no idea how to go about troubleshooting these errors. For instance, I generated a static page loading all the JS files so that I could selectively turn JS off and on by removing the offending JS in the <head> (something I know I can do in FB directly on the dynamic site but I have not figure out how yet). Also I was able to have some load before others and vice versa as the poster suggest. I even run the JQuery compatibility mode but all I could find was pointers to internal parts of the JQuery or Mootools files that really I have no idea how to troubleshoot. Am I supposed to mess around with JQuery? I don;t think so. Waat is frustrating is that many web sites have this IE errors (just take a tour around) especially sites made in Joomla, Drupal, wordpress, etc. Yet it seems to be an underground problem with little direct documentation. Ot it could be I am not searching properly. One of the problems is that Joomla for instance uses an older version of Mootools as part of the core. Most third party add-ons also use Mootools but a newer or different version. But what is one to do? I am not a JS genius, not even a amateur for that matter. I just know how they work and I can (barely) read the code. Definitely I need to become better at it but I don't know how. That's the reason for my post. I am not trying to troubleshoot the individual web sites or libraries, I need to get the hand on how to fix JS errors in general or at least find resources whrre I can learn and/or ask others to help me. In time I can learn by gaining experience. Thank you very much for your post. On Jul 29, 6:43 am, ColinFine <[email protected]> wrote: > On Jul 29, 12:53 pm, ColinFine <[email protected]> wrote: > > > On Jul 29, 3:28 am, conticreative <[email protected]> wrote: > > I don't know JQuery or Mootools, but when this sort of error appears > > in prototype.js, it is usually down to one of three causes: > > > 1. You have passed an element which does not exist to the library > > 2. You are trying to operate on the DOM before it has finished loading > > 3. You are using a new or outlandish browser (eg IE8) and the library > > does not work on it (yet). > > I left out reason 3a (though this one may be specific to prototype.js, > I don't know) > 3a. You are using IE in which DOM objects are not real objects and > don't obey Javascript rules regarding the prototype chain, so you need > to extend them explicitly. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
