119652 - Loading... doesn't show what page is being loaded

Status: RESOLVED EXPIRED

(SeaMonkey :: Tabbed Browser, enhancement)

Description

[Jacek Chmiel]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.7+)
Gecko/20020111
BuildID:    20020111

It's impossible to know what page address is being loaded in a new tab.
With several tabs opened simultaneosly it's a bug - for instance, you don't know
which tab to close if you don't want to wait for the page (slow connection).


Reproducible: Always
Steps to Reproduce:
1. Open page with many links (slow connection, i.e. modem 28K or very busy LAN)
2. click on link with Ctrl to open a new tab
3. repeat 2 many times with different links

Actual Results:  Loading... appears as a title of tab, but... you don't know
which link is being loaded

Expected Results:  Before Mozilla knows the title of the page - she should
display URL (simplified, no protocol:// prefix please)

Comment 1

[Grey Hodge (jX)]

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

Comment 2

[Jacek Chmiel]

It's not the duplicate! Note: I mean "when opening a new tab". I has nothing to
do with the splash screen!

Comment 3

[xyzzy]

Usually the URL doesn't fit into my tabs anyway, so I'd prefer this info in the
tooltip, which seems to just parrot this data anyway.

Something like "Loading http://www.mozilla.org/ ... " might work as a
compromise, but I think it would tend to add clutter.

Comment 4

[Jacek Chmiel]

In my opinion the best solution is message "Opening 'www.mozilla.org'..."
(no http:// prefix which takes some space indeed)

Comment 5

[Diego Biurrun]

Sounds like a reasonable enhancement to me, likely post 1.0 stuff, but nice
polish.  Confirming, marking enhancement, OS=All and all that..

Comment 6

[mental]

See also bug 128145 for an interesting proposal.

Comment 7

[Narayan]

I am still getting this problem with Mozilla v1.3.

When combined with bug#104532, the combination is deadly:
1. The user does not have a clue as to which pages are not getting loaded.
2. He can not refresh thoise pages.
3. The status bar shows a wrong URL (Refer top bug#104532); so he cannot read
the URL from there, too!

BTW, the problem occurred when I tried to launch the query pages for several
bugs simultaneously, from the Bugzilla's very own "step#1" ("check for duplicate
bugs") screen. Reporting for Win NT4.

Comment 8

[Åke Wallebom]

This also applies to non-tabbed links (opening links by just clicking on them).
When clicking on links, the URL in the address bar is not updated until the
complete page has been loaded. This makes it impossible to click Refresh to
retry loading the page.

You can use http://blixten.ake.nu/firefoxbug/ as a test page (has a slow loading
page)

Comment 9

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 10

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420