Closed
Bug 5042
Opened 26 years ago
Closed 25 years ago
Window.defaultStatus can not be accessed.
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
VERIFIED
FIXED
M10
People
(Reporter: desale, Assigned: joki)
Details
(Whiteboard: [TESTCASE] read/write access of window.defaultStatus must be implemented)
Attachments
(1 file)
Window.defaultStatus can not be accessed.
Providing information to simulate the problem.
Product: Seamonkey.[apprunner]
Build Date: 04/13/99
Platform: PC [Windows-95]
Steps to Reproduce:
1] Please copy the code I'm providing. Save as HTML file.
2] Open this HTML file in apprunner.
3] You will find one button called "Check Window defaultStatus".
4] Click this button.
Expected Results: After Clicking button "Check Window DefaultStatus", the result
Text box should show windows default status which is set to word "Seamonkey".
Result Text box should show word "Seamonkey".
Actual Results: Result Text Box does not show anything.
Code:
<html>
<head>
<title>Default Status</title>
</head>
<script>
<!--
function report(text)
{
var value=document.workform.result.value;
var msg= value+ " " +text;
document.workform.result.value=msg;
}
//-->
</script>
<body >
<script>
<!--
window.defaultStatus="Seamonkey";
//-->
</script>
<form name="workform" >
<input type="button" value="Check Window DefaultStatus" name="Reset2"
onClick="report(window.defaultStatus);"><br>
Result Text Box<INPUT TYPE=text NAME="result" SIZE=80>
<input type="reset" value="Reset">
</form>
</body>
</html>
Updated•26 years ago
|
Status: NEW → ASSIGNED
Updated•26 years ago
|
Target Milestone: M6
Updated•25 years ago
|
Assignee: vidur → joki
Status: ASSIGNED → NEW
Target Milestone: M6 → M7
Comment 1•25 years ago
|
||
This one's for Tom....
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M7 → M9
Assignee | ||
Comment 2•25 years ago
|
||
set/get status doesn't work yet in apprunner anyway so even if I fix this now it
won't show. Moving to M9 so I can work on other bugs now.
Updated•25 years ago
|
Whiteboard: [MAKINGTEST] christian@wenz.org
Comment 3•25 years ago
|
||
Updated•25 years ago
|
Whiteboard: [MAKINGTEST] christian@wenz.org → [TESTCASE] read/write access of window.defaultStatus must be implemented
Comment 4•25 years ago
|
||
Overview Description: no access to window.defaultStatus
Steps to reproduce: 1) load attachment; 2) click on "Check Window DefaultStatus"
button
Actual Results: window's status line does not show "Seamonkey"; text edit only
contains whitespace characters
Expected Results: window's status line to show "Seamonkey"; text edit to contain
"SeaMoney".
Build Date & Platform: occurs on M7 and current daily build; does not occur on
NN4.x
Additional Information: didn't tough desale@netscape.com's test case as it
couldn't be simplified much further
Assignee | ||
Comment 5•25 years ago
|
||
So this is partially fixed. They're reflected from JS but I need to find the
guy doing status bar work to get the default status showing up properly.
Assignee | ||
Updated•25 years ago
|
Target Milestone: M9 → M10
Assignee | ||
Comment 6•25 years ago
|
||
Not going to muck with the status bar myself so this won't get fixed in M9.
Reporter | ||
Comment 7•25 years ago
|
||
I just tested this one again, and found that its kinda got fixed. Actually it
got fixed in apprunner, but not in viewer.
Apprunner returns proper results, so there is no problem for apprunner now.
Viewer returns all question marks instead of defaultStatus, so there is still
some problem with viewer.
Apprunner is working fine now.
Builds I used are 08-13-09.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 8•25 years ago
|
||
There are a number of window like things that don't work in viewer. I think
the apprunner part is probably enough. Marking fixed.
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 9•25 years ago
|
||
Its working fine for apprunner, but not for viewer.
As per tom, apprunner part is probably enough.
Marking it verified.
You need to log in
before you can comment on or make changes to this bug.
Description
•