Closed
Bug 109743
Opened 24 years ago
Closed 24 years ago
setting of window.status in onmouseover handler of link fails
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: martin.honnen, Assigned: jst)
Details
Attachments
(1 file)
I am using M 0.9.5 and experience some regression that the setting of
window.status
in the onmouseover handler of a link is ignored. I inserted some test code and
found that the event is fired and the handler executed but setting window.status
is ignored.
Many DOM level 0 sites rely on this so it needs to be fixed.
Here is the test page:
<html>
<head>
<title>
simply onmouseover status message
</title>
<script type="text/javascript">
function outputEvent (evt) {
document.formName.output.value = new Date() + ': ' + evt.type + '\n' +
document.formName.output.value;
}
</script>
</head>
<body>
<a href="http://www.mozilla.org"
onmouseover="outputEvent(event);
window.status = 'Mozilla.org';
return true;"
onmouseout="outputEvent(event);
window.status = '';
return true;"
>
Mozilla
</a>
<br />
<br />
<a href="http://www.mozilla.org"
onmouseover="outputEvent(event);
window.status = 'Mozilla.org';
if (event.preventDefault)
event.preventDefault();"
onmouseout="outputEvent(event);
window.status = '';
if (event.preventDefault)
event.preventDefault();"
>
Mozilla
</a>
<br />
<br />
<br />
<form name="formName">
<textarea name="output" rows="10" cols="80" wrap="off"></textarea>
</form>
</body>
</html>
Mouseover the first link and the status bar should show
Mozilla.org
but simply shows the link's href.
The second link is an attempt at a workaround using the DOM level 2
event.preventDefault() instead of returning true but that workaround doesn't
work either.
The mouseover handler of the first link works as intended with NN4 and IE6,
showing the status message set in the handler.
|
Reporter | |
Comment 1•24 years ago
|
||
|
||
Comment 2•24 years ago
|
||
*** This bug has been marked as a duplicate of 99009 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•