Closed
Bug 1097
Opened 26 years ago
Closed 26 years ago
crypto.signText() and Win16 problem.
Categories
(Core :: JavaScript Engine, defect, P2)
Tracking
()
VERIFIED
WONTFIX
M3
People
(Reporter: pbenes, Assigned: jsw)
Details
I am testing signing function of Netscape Navigator - crypto.signText().
My application has to run on Windows 3.1 ( PC, Pentium 166 MMX, 64 MB RAM ) and
I have met some serious problems. When I try to open this testing page
<html>
<head>
<script>
var foo = crypto.signText("Bill of Sale\n--------------------", "ask");
</script>
</head>
<body> This is an HTML page<p>
<script> document.write(foo);
</script>
</body>
</html>
browser reaction is following:
- Netscape Navigator 4.04. ( WinNT ) .... everything is O.K.
- Netscape Navigator 4.04. ( Win 3.1) .... browser crashes with GPF
- Netscape Navigator 4.07. ( Win 3.1) .... appears EMPTY window,
that refuses to be closed and that is all.
|
||
Updated•26 years ago
|
Assignee: mccabe → jsw
Summary: crypto.SignText() problem
|
|
||
Comment 1•26 years ago
|
||
Reassigning this to Jeff Weinstein, at Norris' recommendation.
Thanks for the excellent bug report - it's a luxury to get such succinct
testcase.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WONTFIX
There are known problems with signtext on windows 3.1, but windows 3.1 is no
longer a supported platform.
Status: RESOLVED → VERIFIED
Summary: crypto.signText() and Win16 problem.
Javacsript component begin retired. Moving this bug to Javascript Engine.
|
||
Comment 6•19 years ago
|
||
This is one of 2 bugs with Windows 3.1 as the OS. Setting to Other so I can nuke that value from the database and stop it from cluttering the menus.
OS: Windows 3.1 → other
You need to log in
before you can comment on or make changes to this bug.
Description
•