Closed
Bug 7253
Opened 25 years ago
Closed 25 years ago
Method which specifies whether data tainting enabled or not does not return anything.
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
VERIFIED
FIXED
M10
People
(Reporter: desale, Assigned: vidur)
Details
(Whiteboard: [TESTCASE] window.navigator.taintEnabled() returns nothing)
Attachments
(1 file)
(deleted),
text/html
|
Details |
Method for identifying whether data tainting is enabled or not does not return
anything.
Javascript method navigator.taintEnabled() is used for testing whether data
tainting is enabled or not so it should return true or false, but it does not
return anything.
Product: seamonkey [Apprunner/ Viewer]
Build: 1999-05-27-08.
Steps to reproduce bug:
1] Please copy code I'm providing. Save it as HTML file.
2] Open this HTML file in viewer as well as apprunner.
3] It should show you whether data tainting is enabled or not.
Expected Results:
TaintEnabled = false or TaintEnabled = true
Actual Results:
TaintEnabled =
CODE:
<html>
<head>
<title>Test Page</title>
</head>
<body >
<form name="workform">
<SCRIPT LANGUAGE="JavaScript1.1">
document.writeln("<h3>");
document.writeln("Navigator Properties");
document.writeln("</h3>");
document.writeln("<br>");
document.writeln("TaintEnabled = ");
document.writeln(window.navigator.taintEnabled());
document.writeln("<br>");
</SCRIPT>
</form>
</body>
</html>
END OF CODE:
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M9
Comment 1•25 years ago
|
||
Updated•25 years ago
|
Whiteboard: [TESTCASE] window.navigator.taintEnabled() returns nothing
Comment 2•25 years ago
|
||
desale's test case cannot be simplified further.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•25 years ago
|
||
Fixed checked in on 9/26/1999. We always return false.
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 4•25 years ago
|
||
Working perfect. Marking verified.
You need to log in
before you can comment on or make changes to this bug.
Description
•