124790 - status line does not change when using javascript "parent.self.status"

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[infinity]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4; en-US; rv:0.9.7) Gecko/20011222
BuildID:    2001122123

The text in the status line should show additional information when using a.e.
<onmouseover="parent.self.status='Informationen ueber hannover.gay-web.de
anzeigen';return true">. Mozilla shows the original link target.



Reproducible: Always
Steps to Reproduce:
1. call the url http://hannover.gay-web.de
2. position mouse over links in the black menu bar
3. check status line

Actual Results:  Original link target is shown.

Expected Results:  Additional information should be shown.

Tested with OS/2 version 0.9.7 and Windows version 0.9.8.

Comment 1

[Boris Zbarsky [:bzbarsky]]

worksforme, linux build 2002-02-07-22...

Comment 2

[david]

I can duplicate this bug with different (simpler) code.  Here's the code that
doesn't work for me:

<a href="sitemap.html" onmouseover="status='Site Map'; return true;">Site Map</a>

When I mouseover this link, I should see "Site Map" in the status line.  But I
see nothing.  The event handler is being triggered, but the status line is not
being updated as requested.  This doesn't work in the Linux 0.99 or in 1.0RC1
builds. If I go way back to Netscape 6.0, it does work, so it is a regression
since then.

Comment 3

[Michael Lefevre]

WFM with 2002091908/trunk/win2k.

reporter: can you reproduce this bug with a recent build of mozilla (for
example, 1.2alpha)? if so, please comment again with details. if not, please
resolve this bug as WORKSFORME. thanks.

Comment 4

[david]

The original poster's website works for me now, too, using Linux and Mozilla 1.1.  
I don't know if he redid his site to workaround the bug or not.

However, the simpler example I provided still does not work for me, again with
Mozilla 1.1 on Linux.

I'll put my testcase up as an attachment.

Comment 5

[david]

Attachment: testcase

Comment 6

[Michael Lefevre]

David - I think your simpler example doesn't work because it's not correct, you
need to use window.status (or parent.self.status as in the original).  "status"
alone seems to work in Internet Explorer, but IE is very generous about guessing
things which aren't there...  if the original site works, you're not seeing this
bug any more.

Comment 7

[david]

window is the global object.

window.status is the same as status.

The example I provided works in Netscape  4 and worked in earlier releases of 
Mozilla.  Something has broken.

The defaultStatus property does still work, FYI.

Comment 8

[Dirk Theurer]

Attachment: onmouseover="*.status='string';return true;" not working.

The original test case does not properly illustrate this bug. None of
top.status, parent.status and self.status work.

Comment 9

[Dirk Theurer]

Comment on attachment 165185 [details]
onmouseover="*.status='string';return true;" not working.

Whoops! Found some other bugs that are similar (all status related). Bug still
exists in FF v1PR, but also includes just status, and window.status.

Comment 10

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420