Closed
Bug 5905
Opened 26 years ago
Closed 25 years ago
if bad link followed x times, back button needs x+1 presses
Categories
(Core Graveyard :: Tracking, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
M15
People
(Reporter: cpratt, Assigned: radha)
References
()
Details
Build ID: 1999050408
Platform tested against: Windows NT
The above URL (occasionally) contains advertisements. If you click on one of
those ads, you should go to the linked site - but this isn't working yet due to
problems with trailing slashes in relative URLs (I think). In any case, if you
go to a site and click on a link that doesn't go anywhere (ie results in an
'Unable to locate host' error), for every time you try to go to that site, you
have to press the Back button one more time to get to the previous site. Just to
make this clear:
- launch the browser
- go to Yahoo! or another site
- go to the above URL
- click on the ad 5 times
- in order to get back to Yahoo!, you now have to click Back 6 times
Updated•26 years ago
|
Assignee: waterson → trudelle
Updated•26 years ago
|
Assignee: trudelle → don
Comment 1•26 years ago
|
||
Sounds like the button works. Over to don.
Assignee: don → radha
Component: RDF → other
Priority: P3 → P2
Target Milestone: M7
Assignee | ||
Comment 3•26 years ago
|
||
I would say this is a feature question. Today in communicator 4.5 if you typed
in a illegal URL in the urlbar and then went on to do other stuff, when you hit
back, several times to get all the way back, you will stumble in to the illegal
url that you typed in. URLs are recorded in the history list irrespective of
whether a page was loaded successfully or not. Do we want to maintain this
behavior or change the beavior so that history has only the successful URLs
visited?
Also, I believe that this problem of "Not going anywhere from the banner ad"
should get fixed eventually, because it works in 4.5.
cc'ing don & karnaze
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•26 years ago
|
Target Milestone: M7 → M11
Assignee | ||
Comment 4•26 years ago
|
||
Moving to future milestone, since there are several ways, this behavior is going
to be affected in the future.
Assignee | ||
Updated•25 years ago
|
Target Milestone: M11 → M15
Assignee | ||
Comment 5•25 years ago
|
||
Since a bunch of things like netcenter integration, a local error page etc...
affect this. I'm moving this out to M15.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•25 years ago
|
||
If a url load fails, it is taken out of session history. That s'd fix this
problem. Please verify
Updated•25 years ago
|
QA Contact: phillip → claudius
Comment 7•25 years ago
|
||
changing qa contact to claudius:
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 8•25 years ago
|
||
VERIFIED fixedfor the 1999110809 builds
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•