Closed
Bug 147410
Opened 23 years ago
Closed 23 years ago
JavaScript: unable to set self.defaultStatus
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: htrdang, Assigned: jst)
Details
Attachments
(1 file)
|
239 bytes,
text/html
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3)
Gecko/20020523
BuildID: 20020523
Can't set the text in the status bar. The code below works fine in IE but not
Mozilla. When opened, it shows only the first alert. In the JavaScript console,
the following error is displayed:
Error: uncaught exception: Permission denied to set property Window.defaultStatus
I figured that my settings in Preferences/Advanced/Scripts disallowed changing
the status bar's text, so I toggled it. No matter what I allowed, still the same
result.
--------------------------
<html>
<head>
<SCRIPT LANGUAGE="JavaScript">
<!--
function setStatus(msg)
{
alert('1');
self.defaultStatus = msg;
alert('2');
}
setStatus('blah blah');
//-->
</SCRIPT>
</head>
<body>
Hello World!
</body>
</html>
Reproducible: Always
Steps to Reproduce:
1.Make sure the browser allow webpages to change status bar's text
(Preferences/Advanced/Scripts)
2.Open the file in browser, only the first alert will show up
3.Open the JavaScript Console to see the exception
Actual Results: Only alert #1 showed up. Status bar's text not changed.
Exception displayed in JS Console.
Expected Results: Shows first alert. Status bar's text set to "blah blah".
Shows second alert.
|
Reporter | |
Comment 1•23 years ago
|
||
|
||
Comment 2•23 years ago
|
||
Browser, not engine ---> DOM Level 0
Assignee: rogerl → jst
Component: JavaScript Engine → DOM Level 0
QA Contact: pschwartau → desale
|
|
||
Comment 3•23 years ago
|
||
This WORKSFORME using Mozilla trunk binaries on WinNT, both from
around the date of this bug report (20020520) and currently.
Sometimes there are obscure preference problems that cannot be
toggled by the Edit > Preferences GUI, but have to be done by
hand in the Mozilla files "all.js" or "prefs.js".
Luke:
1. Does the problem still occur with a current Mozilla build?
2. If it does, try running Mozilla under a new profile. You can
always bring up the Profile Manager by launching Mozilla from
a console this way:
[(path to Mozilla)]./mozilla -profilemanager
Once that comes up, you can create a new profile. This will
give you a fresh set of preferences...
|
Assignee | |
Comment 4•23 years ago
|
||
WORKSFORME, please try with a new profile and if it's still a problem reopen
this bug...
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•