298724 - Javascript won't work

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[António Poças]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

With my previous Firefox profile (I had to delete it due to this bug),
javascript wouldn't work. If I tried to open a javascript popup, like the one in
the URL, it wouldn't do anything, and whenever I closed the browser after
running, I had to close the process in the task manager.

Reproducible: Sometimes

Steps to Reproduce:
This bug needs a buggy/broken profile to be repeated. If you have one, Firefox
won't run any javascript.

Actual Results:  
Nothing.

Expected Results:  
Popup a window, in the case of the URL I gave.

Comment 1

[Adam Guthrie]

Have you configured the JavaScript options in Tools > Options > Privacy > JS?

Comment 2

[António Poças]

(In reply to comment #1)
> Have you configured the JavaScript options in Tools > Options > Privacy > JS?

Didn't change any defaults. It just stopped working.

Comment 3

[Adam Guthrie]

Download a build from this link:
http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ and make
a clean profile and see if you can reproduce this. Note: this may just be caused
by buggy JS on specific site that you're visiting.

Comment 4

[António Poças]

(In reply to comment #3)
> Download a build from this link:
> http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ and make
> a clean profile and see if you can reproduce this. Note: this may just be caused
> by buggy JS on specific site that you're visiting.

I'll do that. But I'm pretty sure it's not buggy JS, since it happened with all
JS, including sites that worked before.

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Adam Guthrie]

JS works fine; this was just an isolated incident caused by bad user
configuration or a conflicting extension.