123051 - javascript source file apparently not loading, functions not accessible

Status: RESOLVED DUPLICATE of bug 118404

(SeaMonkey :: General, defect)

Description

[Matthew Rasnake]

Description:
This error has affected all (nightly) builds i've tested since 4 or 8 days after
release of 0.9.7.
I use JavaScript source files frequently, and in 0.9.7, IE, and NS4x, i get no
errors with the scripts on the pages of the URL provided. in builds later than
0.9.7, the mechanism that loads external JavaScript source files would appear to
be broken, as the functions are not seen by the page when triggered by rollover
(and other) events.


Reproducibility:
Every Time


Steps to Reproduce:
1. Load Mozilla build greater than 0.9.7 (+4 days or so)
2. go to http://www.corvusdigital.com/


Actual Results:
JavaScript console reported "selMenu not defined" rollovers on the main menu
(upper right corner) didn't work.


Expected Results:
the onLoad handler of the body tag should have called selMenu() (which would do
nothing since it's on the home page). then the square box images to the right of
the menu item text should have changed as the menu items are rolled over by the
mouse.

Comment 1

[Phil Schwartau]

Not JS Engine. Reassigning to Parser as in bug 118404,
"External JS files not loading; fixed by making new Profile"

This looks like a duplicate. Matthew, could you try the solution at
http://bugzilla.mozilla.org/show_bug.cgi?id=118404#c75 ?

If that works, you can resolve this bug as a duplicate of bug 118404;
thanks -

Comment 2

[Phil Schwartau]

Note: the file you need to find is called "prefs.js" (or perhaps "all.js").
One of these files should have the bad line discovered in bug 118404.

Comment 3

[harishd]

Phil: Bug 118404 is not a parser bug. It turns out that the bug is in the script
loader. I'm neither sure to whom this bug should go ( <guess> jst </guess> ) nor
to which component it should belong. 

Comment 4

[Phil Schwartau]

OK, reassigning to Browser-General for now; cc'ing jst.

Matthew: I see that bug 118404 has just been fixed this afternoon.
So tomorrow's build might simply work without you having to try any
experiments on your own.

Let's hope, anyway -

Comment 5

[Matthew Rasnake]

The fix for 118404 would certainly appear to have also fixed this bug.
Seeing as this is my first officially reported bug, and i'm still a bit sketchy
on procedure, i'll let someone with more authority mark this as a fixed/dupe bug.

Thanks for the assistance guys!

Comment 6

[Phil Schwartau]

Matthew: thanks. Based on your findings, marking this as a duplicate.
Thank you for using Bugzilla!



*** This bug has been marked as a duplicate of 118404 ***