Further to Jeff's post, here are some more things that jump out immediately as being potential hot-spots:
- Your "obfuscated" JS (which doesn't look that obfuscated IMHO) seems to be around 160Kb on one line (i.e. with no line breaks). I know from personal experience that this can cause slow parsing issues in some browsers. So, try putting line breaks in between each function and see if that helps.
- While you have them after
most, you do not have ";" delimiters after
all your function code. I have been bitten by this before, specifically in Safari, specifically on a JS-intensive app. So, make sure you put semicolons after all of your function close braces.
Some points to note:
- Before trying these, make sure you clear your cache. If you don't, you will not be able to guarantee that any fixes will have been picked up by the browser.
- Why bother with "obfuscation" anyway? As I mentioned earlier, your apparently "obfuscated" code doesn't look very obfuscated. It look like you've simply removed line breaks. This begs the question, why have you obfuscated the code? Given that no matter how well you think you can hide your code, you will [!]never[/!] be able to (trust me on this), give up while you're ahead. See:
faq215-3101
faq216-5090
faq216-355
- Why not set up Rhino or JWebUnit, etc to do some validation of your JS code as part of your automated build process (you do have one of these, right?)
Dan
Coedit Limited - Delivering standards compliant, accessible web solutions
[tt]Dan's Page [blue]@[/blue] Code Couch
[/tt]