99009 - window.status not functional

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Description

[Cringer]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.3+) Gecko/20010909
BuildID:    2001090908

The OnMouseOver event on my site is supposed to make the window status display
text for the link your mouse is over rather than showing the ugly URL's. 
Javascript is enabled, however, it does not fire this even, and thus you are
shown only the URL in the status bar instead of the text that was coded.  Here
is my code:

<a OnMouseOver="window.status='Show My Text';return true"
OnMouseOut="window.status=''" href="pagelink.html">Show My Link</a>
This code will work on 0.9.3 build 2001080103 [8-1-2001]

Reproducible: Always
Steps to Reproduce:
Go to the site and move the mouse over a link.


Actual Results:  The same results.

Expected Results:  Expected for the OnMouseOver command to display the given
text in the status bar of the window.

Comment 1

[Markus Gerstel]

Confirmed with linux 2001090913 (OS->All), but
<a OnMouseOver="alert(window.status);" href="pagelink.html">Annoy Me</a>
shows us that onmouseover works as it should. On the contrary, window.status
does not. -> Updating Summary

Comment 2

[Boris Zbarsky [:bzbarsky]]

Over to dom0

Comment 3

[Fabian Guisset]

See also bug 90105 and bug 78798. Argh.

Comment 4

[Alfonso Martinez]

*** Bug 103066 has been marked as a duplicate of this bug. ***

Comment 5

[Tuukka Tolvanen (sp3000)]

*** Bug 101491 has been marked as a duplicate of this bug. ***

Comment 6

[Markus Gerstel]

Attachment: simple testcase

Comment 7

[Boris Zbarsky [:bzbarsky]]

*** Bug 109743 has been marked as a duplicate of this bug. ***

Comment 8

[Boris Zbarsky [:bzbarsky]]

*** Bug 106113 has been marked as a duplicate of this bug. ***

Comment 9

[Boris Zbarsky [:bzbarsky]]

*** Bug 112066 has been marked as a duplicate of this bug. ***

Comment 10

[Phil Schwartau]

*** Bug 112416 has been marked as a duplicate of this bug. ***

Comment 11

[Johnny Stenback (:jst)]

Over to jag, the DOM code does the right thing, but our chrome decides not to
show the status correctly. I see jag's fingerprints all over the chrome code
that deals with this, reassigning.

This is definately a mozilla1.0 stopper.

Comment 12

[Brendan Eich [:brendan]]

Any relation to bug 112366?

/be

Comment 13

[Brendan Eich [:brendan]]

Ok, now that bug 112366 is fixed, is this still busted?  Or was it a (forward) dup?

/be

Comment 14

[Boris Zbarsky [:bzbarsky]]

*** Bug 117459 has been marked as a duplicate of this bug. ***

Comment 15

[Johnny Stenback (:jst)]

Jag, could you please have a look at this or assign to someone else who knows
the XUL code that deals with this?

Comment 16

[jag (Peter Annema)]

Attachment: Put jsStatus and status before overLink, remove manually clearing jsStatus.

This should do the trick. use the url to test, the "simple testcase" merely
pops up an alert with the current window.status, it doesn't test setting it
from a mouseover.

Comment 17

[Christopher Aillon (sabbatical, not receiving bugmail)]

Comment on attachment 63219 [details] [diff] [review]
Put jsStatus and status before overLink, remove manually clearing jsStatus.

<caillon> jag: remove the comment above that :)
<caillon> >	// set empty so defaults show up next change
<caillon> >-	this.jsStatus = "";
<jag> caillon: duh
<jag> done
<caillon> jag: r=me after that :)

Comment 18

[Johnny Stenback (:jst)]

Comment on attachment 63219 [details] [diff] [review]
Put jsStatus and status before overLink, remove manually clearing jsStatus.

sr=jst

Comment 19

[jag (Peter Annema)]

Attachment: Slightly different version which keeps overLink ahead of status

Comment 20

[jag (Peter Annema)]

Comment on attachment 63221 [details] [diff] [review]
Slightly different version which keeps overLink ahead of status

caillon said r=caillon

Comment 21

[jag (Peter Annema)]

Checked in.

Comment 22

[rbs]

*** Bug 81917 has been marked as a duplicate of this bug. ***

Comment 23

[jag (Peter Annema)]

Some interesting findings in bug 117857. Most importantly, neither NS4.x on
Windows nor IE6 support changing window.status from onmouseover on <a href>,
instead they display the value of the href, like we did before I checked in this
patch.

Comment 24

[jag (Peter Annema)]

Ha!

Comment 25

[Sébastien Delahaye]

#23, I just tested that with NS4.78 and MSIE 6, and _both_ display the text
contained in the windows.status on onmouseover, not the URI.
This bug is fixed, Mozilla now handles window.status like it did months ago, it
should be marked as Fixed.

Comment 26

[jag (Peter Annema)]

Actually, my test was flawed. The test I was using was

<a href="link.html" onmouseover="window.status='some text'">link</a>

This won't show "some text" but instead "link.html". If however you add a return 
true, then it does like described by the reporter, thus:

<a href="link.html" onmouseover="window.status='some text'; return 
true">link</a>

Mozilla currently will display "some text" in both cases, instead of only in the 
second case. See the last testcase on bug 117857 for a demonstration of both.

Since the checkin for this bug wasn't quite what we wanted, I've reopened this 
bug to make sure everything still works when the fix for bug 117857 lands (part 
of which will undo part of the patch that went in for this bug).

Comment 27

[jag (Peter Annema)]

Checked in.