Today Nithiwat called me over to help him figure out why his Parser object wouldn’t load via our wm_require() function which loads javascript on-demand if the object is not found. We figured out the problem fairly quickly, but learned one very important lesson: Prefix all global objects with something you know no one else will use.
Apparently in Firefox there is a native Parser object (which I can’t find a reference for). In the past, we loaded our Parser.js file with no problem, as it simply overwrote the native object. Obviously that doesn’t work anymore. So it’s going in our newly formed wack library.
I can’t wait to tell people what that stands for…