97641 - reload does nothing after moz fails to connect to home page (or first page in a window)

Status: RESOLVED DUPLICATE of bug 28586

(SeaMonkey :: General, defect)

Description

[John Levon]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3+) Gecko/20010823
BuildID:    2001082308

If I go to e.g. www.example.com, I'll get a conn refused message (same problem
with a dns entry that doesn't exist)

When I press reload, nothin happens.

This is a usability issue when e.g. my ppp goes down, and the conn times out.

When I bring the connection back up, reload does nothing. It should in fact
try again, since it will connect this time.

Reproducible: Always
Steps to Reproduce:
1. go to www.mmmmmmefeefewfwefwefewf.com
2. close alert
3. press reload

Actual Results:  should try again

Expected Results:  doesn't try again

Comment 1

[Jerome Lacoste]

I was going to report a bug thaty I think is the same as that one. Here is my
feedback pasted. I think that this bug should be either confirmed as I didn't
find any duplicate in the result of a Bugzilla query with keyword 'reload'.

Subject: Reload doesn't work when hitting the reload icon if previously attemp
failed

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20010913
BuildID:    2001091303

When I start Mozilla without my modem connection up, I get an error message and
a blank page instead of my home page (www.mozilla.com/start)
Then I start the connection and click the reload icon. The page does not get
connected.
I presume that the fact that the connection goes up or down does not affect the
reloading mechanism of the cache, that's why I've put the bug in the Cache
category. Please confirm.

Reproducible: Always
Steps to Reproduce:
1. Start Mozilla. Mozilla tries to load the home page which is a remote page for
me. Loading fails and display a blank page.
2. Start up modem/Internet connection 
3. click reload

Actual Results:  Page is not reloaded

Expected Results:  Page should be reloaded

Comment 2

[Jesse Ruderman]

This could be fixed by fixing bug 28586, "Should use placeholder error page, 
not dialog, for inaccessible pages".

Comment 3

[Jesse Ruderman]

I can reproduce this bug on Win98 by middle-clicking on a link to 
http://localhost/.  Mozilla brings up a dialog saying it couldn't connect, but 
after I dismiss the dialog, the reload button doesn't do anything.

Workaround: focus the location bar by pressing Ctrl+L, and then press enter.

-> Session history

Comment 4

[benc]

Hmm, I would imagine it's actually XP apps, b/c there is a "current" URL value
(not the same as what is in the location bar. Reload points to that value.

Comment 5

[Jesse Ruderman]

Btw, the page isn't added to session history either.  If I middle-click a 
broken link and then hit the home button, the back button doesn't become 
enabled.

Comment 6

[Radha on family leave (not reading bugmail)]

Giving to darin. This may be fixed by a recent change he made to the loadflags
for reload.

Comment 7

[Darin Fisher]

WORKSFORME - 20011017/08 linux

Comment 8

[Darin Fisher]

actually, reopening... i was testing something different.  i can confirm this
bug report... seems like we reload the old URL instead of the "bad" one just typed.

Comment 9

[Darin Fisher]

-> future

Comment 10

[Boris Zbarsky [:bzbarsky]]

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

Comment 11

[[e-mail]]

+ mozilla 1.0
Typing in an incorrect DNS hostname triggers this problem (VPN or un-dialed
users typing FQDN's they can't see immediately in DNS).

This bug happens to me all the time, and it is driving me crazy. Since there is
only one duplicate, then it must be a duplicate of something else. This is
marked future, but it really should be fixed in a mozilla 1.0 timeframe.

I want this bug re-triaged for its final component (I doubt this is cache), so
I'm sending it back to browser-general. IMO, this is one of those Navigator
app/Doc Shell/XP-GUI App things I should know more about. 

Comment 12

[[e-mail]]

set owner & qa to default (to increase visibility w/ queries that use defaults)

Comment 13

[Boris Zbarsky [:bzbarsky]]

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

Comment 14

[Boris Zbarsky [:bzbarsky]]

I know there are more duplicates.  I've seen them.  I just can't find them...
jag, any ideas what's up here?

Comment 15

[Jesse Ruderman]

See also bug 125772, "Reload button should be disabled until URL starts loading".

Bug 95897, "the first URL in a new window isn't added to session history until
it starts loading", is similar to this bug.  95897 also wants the first URL to
not be lost if the user selects a bookmark after moz fails to connect to the
first page in a window.  (Note that neither suggestion from bug 95897 is
consistent with how session history works in general, so wontfixing it in favor
of bug 28586 and/or this bug is reasonable.)

I think this bug should be marked as a duplicate of bug 28586.

Comment 16

[John Levon]

Hmm, I didn't realise it was that difficult to do !

I'm happy with duping this to the the error page bug if you wish (I'm
the reporter). I was aware of that bug before entering this one though,
as long as reload then does something sensible.

One thing that worries me is that this has moz1.0 keyword and that bug
is futured. I really do see this awfully regularly as I'm on dialup. But
on the flip side, navigating to the url bar and pressing return isn't a
great burden for me.

Comment 17

[Asa Dotzler [:asa]]

*** This bug has been marked as a duplicate of 28586 ***