211879 - Location bar empty until page rendering started

Status: RESOLVED DUPLICATE of bug 231393

(Firefox :: Toolbars and Customization, defect)

Description

[bugzilla2005]

User-Agent:       Mozilla/5.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030706 Mozilla Firebird/0.6

When opening a link in a new tab (and possibly window, haven't checked that),
the location bar in the new tab does not get filled in until page rendering is
started.  This way, there is a possibly long phase during loading, when the user
has no information in the tab about what URL is being loaded.  When page loading
fails (without a server-side error page, e.g dns or network error), or the user
chooses to cancel loading (possibly because he wants to try again later), the
URL is lost, and `about:blank' is displayed instead, making it much more
difficult to try again loading the page later.

A common usage pattern when this bug is really annoying, is when you are reading
a page and opening lots of links in the background in new tabs, for reading them
after you have finished with the current one.  When iterating over the new tabs,
if some of them failed to load, you have no idea what URL it was, and cannot try
 reloading it.  

Mozilla 1.4 does not have this bug, i.e. it fills the location bar before
starting to load the page.

See also non-Firebird bug 191145.

Reproducible: Always

Steps to Reproduce:
Open an unreachable URL in a new tab.

Comment 1

[Pham]

I would've reported this long ago but didn't because I thought there was a bug
about this already

but wat about http://bugzilla.mozilla.org/show_bug.cgi?id=170216

Comment 2

[José Jeria]

Duping to bug 203102 (newer but has a patch). Please reopen if you disagree that
this is not the same issue.

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

Comment 3

[Simon Paquet [:sipaq]]

Taking QA Contact

Comment 4

[Mike Connor [:mconnor]]

Verified using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b)
Gecko/20030817 Mozilla Firebird/0.6.1+

Comment 5

[bugzilla2005]

Bug 203102 is marked as fixed, but this problem persisted.

Comment 6

[José Jeria]

Bug 231393 is a newer bug with more information about this. Same issue? If yes,
then dupe this one to that one.

Comment 7

[bugzilla2005]

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