Closed
Bug 4600
Opened 26 years ago
Closed 26 years ago
Can not access the description of any plugin in plugins array.
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
People
(Reporter: desale, Assigned: vidur)
Details
Can not access the description of any plugin in plugins array.
Providing information to simulate the problem.
Product: Seamonkey.[apprunner as well as viewer]
Build Date: 03/31/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 as well as viewer.
3] You will see one button called "Check Plugin Description". Click this
button.
Expected Results: After clicking button "Check Plugin Description", Result
text Box should reflect the description of the first plugin in plugins array.
Actual Results: Result Text Box does not show anything.
Code:
<html>
<head>
<title>Plugins description test</title>
</head>
<script>
<!--
function report(text)
{
var value=document.workform.result.value;
var msg= value+ " " +text;
document.workform.result.value=msg;
}
//-->
</script>
<body >
<form name="workform" >
<input type="button" value="Check Plugin Description" name="Reset2"
onClick="report(window.navigator.plugins[0].description)"><br>
Result Text Box<INPUT TYPE=text NAME="result" SIZE=80>
<input type="reset" value="Reset">
</form>
</body>
</html>
|
Reporter | |
Updated•26 years ago
|
Whiteboard: Can not access the description of any plugin in plugins array.
|
||
Updated•26 years ago
|
Summary: Can not access the description of any plugin in plugins array.
Whiteboard: Can not access the description of any plugin in plugins array.
|
Assignee | |
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
|
|
Assignee | |
Comment 1•26 years ago
|
||
Consolidating all plugins array bugs.
*** This bug has been marked as a duplicate of 4592 ***
|
|
Reporter | |
Updated•26 years ago
|
Status: RESOLVED → CLOSED
|
|
Reporter | |
Comment 2•26 years ago
|
||
Since Plugin array is not implemented so in that case this bug is duplicate of
bug#4592. So closing this bug.
You need to log in
before you can comment on or make changes to this bug.
Description
•