Closed Bug 31997 Opened 24 years ago Closed 24 years ago

Statusbar text set via JavaScript persists over session

Categories

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

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: caseyperkins, Assigned: jst)

References

()

Details

(Keywords: testcase, Whiteboard: [nsbeta2-][nsbeta3+])

Attachments

(1 file)

Status bar messages set by window.defaultStatus carry over to other, non-related 
pages. Try visiting www.people.memphis.edu/~trainlib/documentation, hover the 
mouse over the page, then go to www.yahoo.com. The status bar message set by 
window.defaultStatus remains.
Reassign to DOM 0.
Assignee: rogerl → jst
Component: Javascript Engine → DOM Level 0
QA Contact: rginda → desale
*** Bug 30217 has been marked as a duplicate of this bug. ***
I checked this bug again with a recent build and found that now, the text 
generated by window.defaultStatus doesn't display at all!
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 35013 has been marked as a duplicate of this bug. ***
*** Bug 35602 has been marked as a duplicate of this bug. ***
Travis, I think this is due to your webshell API changes, could you have a look?
Assignee: jst → travis
Actually, this is due to the fact that I changed navigator to properly show the 
default message when it's set.  The problem is the dom window code isn't 
clearing out the default message on the change to a new location.  Flipping 
back to jst to make the dom window code properly set the default message to 
null upon changing pages.
Assignee: travis → jst
*** Bug 36393 has been marked as a duplicate of this bug. ***
One comment on this problem.  It seems to happen when you set
window.content.status="something".
What seems to be happening is that window.content.status never gets reset to the
empty string.   Okay,
you already know this, but I have some other stuff to add:

The situation is further exacerbated by the fact that in the XUL, jsStatus is
the first thing checked by
the function UpdateStatusField.

What you can do to work around it is to modify the function
nsXULBrowserWindow.setDefaultStatus so
that it resets the value of jsStatus; ie: insert the line jsStatus=null; right
before the call to
UpdateStatusField()

I'm not saying that this is the place to fix the problem, but it does the trick.

Andrew.

Hardly a beta stopper, M18.
Status: NEW → ASSIGNED
Target Milestone: --- → M18
*** Bug 40638 has been marked as a duplicate of this bug. ***
*** Bug 40295 has been marked as a duplicate of this bug. ***
*** Bug 41326 has been marked as a duplicate of this bug. ***
*** Bug 37550 has been marked as a duplicate of this bug. ***
*** Bug 42062 has been marked as a duplicate of this bug. ***
*** Bug 31138 has been marked as a duplicate of this bug. ***
The dups of this bug seem to vary a bit -- this may (but may not) be multiple 
bugs.  However, it's quite annoying (and wrong) to have the status bar carry 
over to other pages.  (Could it be seen as a security problem too??)  Thus, 
nominating nsbeta3.
Keywords: nsbeta3
adding mostfreq keyword.  this would be nice to have in nsbeta2 though...
Keywords: mostfreq
*** Bug 42908 has been marked as a duplicate of this bug. ***
I would like to nominate this as nsbeta2 and see what pdt has to say about it.  
The doubleclicks of the world are going to have a field-day when they discover 
this bug -- we will be giving them free persistent billboard space for their 
ads.  See my comments in dup bug 42908.
Keywords: nsbeta2
Marking nsbeta2-.  The adverse effects from this are minimal, though we should 
fix this in beta 3.  It is already nominated as such.
Whiteboard: [nsbeta2-]
*** Bug 43165 has been marked as a duplicate of this bug. ***
*** Bug 43139 has been marked as a duplicate of this bug. ***
This could be a security problem...sort of acts like a session cookie, allows 
information to persist as the user visits different pages. Let's please get this 
fixed by beta3.
*** Bug 38381 has been marked as a duplicate of this bug. ***
*** Bug 43140 has been marked as a duplicate of this bug. ***
*** Bug 44747 has been marked as a duplicate of this bug. ***
*** Bug 45548 has been marked as a duplicate of this bug. ***
*** Bug 45780 has been marked as a duplicate of this bug. ***
clarifying summary a little.  also, this is XP...
OS: Windows 95 → All
Hardware: PC → All
Summary: window.defaultStatus message carries over to other pages → Statusbar text set by JavaScript persists throughout session
Retitling again, since new title was too general.  This is only text set via
window.defaultStatus, not window.status.
Summary: Statusbar text set by JavaScript persists throughout session → Statusbar text set as defaultStatus persists over session
No, I don't think so.  See some of the dups of this bug that mention 
document.status and window.status being affected as well: 43140, 42908, 37550, 
40295, 40638, and 35602.  See even aagno@cs.toronto.edu's 5/2 comment in this 
bug that suggests that window.content.status is also affected.
Summary: Statusbar text set as defaultStatus persists over session → Statusbar text set via JavaScript persists over session
*** Bug 46600 has been marked as a duplicate of this bug. ***
*** Bug 46945 has been marked as a duplicate of this bug. ***
*** Bug 47450 has been marked as a duplicate of this bug. ***
Marking nsbeta3+
Whiteboard: [nsbeta2-] → [nsbeta2-][nsbeta3+]
*** Bug 48317 has been marked as a duplicate of this bug. ***
*** Bug 48596 has been marked as a duplicate of this bug. ***
Keywords: testcase
*** Bug 49136 has been marked as a duplicate of this bug. ***
*** Bug 49469 has been marked as a duplicate of this bug. ***
*** Bug 49538 has been marked as a duplicate of this bug. ***
Priority: P3 → P1
*** Bug 50110 has been marked as a duplicate of this bug. ***
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
*** Bug 50735 has been marked as a duplicate of this bug. ***
*** Bug 50902 has been marked as a duplicate of this bug. ***
Linux 2000090208

The persistence of Statusbar text is fixed ONLY when the page is
changed/reloaded.

In this bug report there is also another issue, see bug 48317 (duped to this
one).

The persistence of status-bar messages is still here when the page is not
changed/reloaded, for ex. in  onmouseover="window.status=...

See testcase reported from bug 48317:

http://www.ugcs.caltech.edu/~iraqispy/test.html

Which bug have I to reopen?
Verified with 2000-091309. Marking verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: