Javascript no prompt if wallet.crypto is true

RESOLVED INVALID

Status

RESOLVED INVALID
11 years ago
9 years ago

People

(Reporter: jukka.mozilla, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071030 MultiZilla/1.8.3.4b SeaMonkey/1.1.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071030 MultiZilla/1.8.3.4b SeaMonkey/1.1.6b SeaMonkey/1.1.6

http://forums.mozillazine.org/viewtopic.php?t=603549

After updated Mozilla 1.7.x to Seamonkey 1.1.5 (later updated 1.1.6), prompt not work ? If change prompt -> alert, works fine.

Example:

<HTML>
<SCRIPT>
function a()
{
var p = prompt("Input:","");

}
</SCRIPT>
<BODY>
AAAAA

</BODY>
</HTML>

But if I set wallet.crypto false, prompt works fine. 



Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Actual Results:  
no prompt

Expected Results:  
prompt

Comment 1

11 years ago
well... a couple things.  First, your testcase shouldn't trigger a dialog.  Nothing calls a().  If a add that, I get a dialog.

Second, please try without Multizilla (and any other extension you have installed).
Version: unspecified → 1.8 Branch
(Reporter)

Comment 2

11 years ago
I mistake cut-paste, didn't look ...

This is original line. I have not Multizilla.
I have already installed twice, I also install 2.0apre1 without plugins, same result. I didn't look what stuff 2.0 installation copy. 

<a href="" onclick="a();">AAAAA</a><br />
(Reporter)

Comment 3

11 years ago
And now I have removed all my extensions. Same result. I have retstarted browser. Works still same way.

Comment 4

11 years ago
> <a href="" onclick="a();">AAAAA</a><br />

This worksforme with 1.1.6 and current trunk.

Do you see any errors in the error console?
Assignee: general → guifeatures
Component: General → XP Apps: GUI Features
QA Contact: general
Version: 1.8 Branch → Trunk
(Reporter)

Comment 5

11 years ago
Nothing when I do this. 

But I just looked after startup (installed again plugins)

1 err
Error: this.docShell has no properties
Source File: chrome://global/content/bindings/browser.xml
Line: 0

Some warn like this:

Warning: trailing comma is not legal in ECMA-262 object initializers
Source File: chrome://inspectorwidget/content/inspectorwidget.js
Line: 85
Source Code:
};
Warning: Failed to load overlay from chrome://stylish/content/browserOverlay.xul.
Source File: chrome://navigator/content/navigator.xul
Line: 0
Warning: Failed to load overlay from chrome://colorzilla/content/colorzillaOverlay.xul.
Source File: chrome://navigator/content/navigator.xul
Line: 0
Warning: Failed to load overlay from chrome://stylish/content/mailOverlay.xul.
Source File: chrome://messenger/content/messenger.xul
Line: 0

Also Javascript debugger is only "titlewindow" and can't stop it.

(Reporter)

Comment 6

11 years ago
I found the solution.
If you have stored password from the same host as your prompt-page, then popup not works. It looks that some other javascript feature are also "nop" if you have stored password in same host. After I remove all stored password, where the host was the same, prompt works fine. Maybe this is some security, but my opinion is that this is bug.

-jukka-
(Reporter)

Comment 7

11 years ago
or ... some problem in the password database ? because after those three lines removing from the password store, all other pages which didn't work correctly, works now fine, even host is something ...

-jukka-

Comment 8

11 years ago
> or ... some problem in the password database ?

Yes, that's possible.  Unfortunately, the bug we'd really like to fix is the one that caused the corruption.  Do you still have the corrupted version of the file?
(Reporter)

Comment 9

11 years ago
I done more testing. If there are settings, where the host is empty, then you have problem. 
Here is example (xxxx.s file):
#2c
.

\=username=\
-crypted username-
*\=password=\
-crypted password-
.
Filter "spam" on "guifeatures-nobody-20080610".
Assignee: guifeatures → nobody
QA Contact: guifeatures

Updated

11 years ago
Component: XP Apps: GUI Features → UI Design
Bug 390025 removed wallet.crypto in SM 2.0.

What is left of this bug, in SM 1.1.x or 2.0?
Depends on: 390025

Comment 12

9 years ago
wallet.* isn't used in SeaMonkey 2.0, and SeaMonkey 1.1 is EOL. Closing bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.