Closed
Bug 156871
Opened 23 years ago
Closed 23 years ago
javascript REFRESH script doesn't work in Mozilla
Categories
(Core :: DOM: Core & HTML, defect, P4)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla1.4alpha
People
(Reporter: tenfourzero, Assigned: jst)
References
()
Details
(Whiteboard: [HAVE FIX])
Attachments
(1 file)
|
1.03 KB,
patch
|
sicking
:
review+
peterv
:
superreview+
|
Details | Diff | Splinter Review |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530
BuildID: 2002053012
The javascript refresh script doesn't function at all in Mozilla:
javascript:history.go()
An example of this is at:
http://javascript.internet.com/buttons/refresh-button.html
Reproducible: Always
Steps to Reproduce:
1. visit url (http://javascript.internet.com/buttons/refresh-button.html)
2. click the button as described on page
3. sigh
Actual Results: nothing :(
Expected Results: refreshed the page
As a button or a text link, this script fails to function at all.
Comment 1•23 years ago
|
||
->DOM0. What is history.go()?
Assignee: rogerl → jst
Component: JavaScript Engine → DOM Level 0
QA Contact: pschwartau → desale
Comment 2•23 years ago
|
||
Shouldn't it be
history.go(0);
to reload the page?
A HREF='javascript:history.go()' doesn't work (an anchor take).
| Assignee | ||
Comment 4•23 years ago
|
||
Does NS4x and IE let you call history.go() w/o any arguments?
Comment 5•23 years ago
|
||
IE yes, Netscape 4 no
| Assignee | ||
Comment 6•23 years ago
|
||
Hmm, do we know of any real sites that are broken due to this?
Comment 7•23 years ago
|
||
I haven't seen any sites with problems due to this. Doron/Marcio?
Comment 8•23 years ago
|
||
Valid Javascript requires a parameter in history.go()... it doesn't even make
sense otherwise. Where is the browser supposed to go, if the script doesn't
tell it?
A Google search indicates that one should use either history.go(0) or
location.reload(true) to refetch a webpage.
Because of this, I am resolving this bug as WONTFIX, since history.go() doesn't
seem like valid Javascript member function. If anyone can find Javascript
specifications that indicate otherwise, feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Comment 9•23 years ago
|
||
Not that I know that this really matters, but it's easy enough to fix, so I'm
gonna attach a trivial patch that makes history.go() === history.go(0), just for
compliance with IE.
Severity: major → normal
Status: RESOLVED → UNCONFIRMED
OS: Windows 98 → All
Priority: -- → P4
Hardware: PC → All
Resolution: WONTFIX → ---
Target Milestone: --- → mozilla1.4alpha
| Assignee | ||
Comment 10•23 years ago
|
||
| Assignee | ||
Updated•23 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Whiteboard: [HAVE FIX]
| Assignee | ||
Updated•23 years ago
|
Attachment #116887 -
Flags: superreview?(peterv)
Attachment #116887 -
Flags: review?(bugmail)
Comment on attachment 116887 [details] [diff] [review]
Make history.go() same as history.go(0)
r=sicking, though i'd be perfectly fine with not landing this too
Attachment #116887 -
Flags: review?(bugmail) → review+
Comment 12•23 years ago
|
||
Comment on attachment 116887 [details] [diff] [review]
Make history.go() same as history.go(0)
sr=peterv, though i'd be perfectly fine with not landing this too
Attachment #116887 -
Flags: superreview?(peterv) → superreview+
| Assignee | ||
Comment 13•23 years ago
|
||
Fix checked in, for better or worse...
FIXED.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•