external links blocking correct address in location, instead leaving undefined

RESOLVED FIXED

Status

()

Firefox
General
RESOLVED FIXED
15 years ago
14 years ago

People

(Reporter: Jonathan Greene, Assigned: Blake Ross)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1

I am not sure what causes this, but I am noticing that many (not all) external
links are creating new windows with the location bar "blocked."  I can see that
there is information there, but not anything useful.  It simply says
"undefined."  There does not seem to be any way to see the actual url.

Reproducible: Always

Steps to Reproduce:
1.click link from email - entourage or Thunderbird
2.see undefined in location bar
3.repeat

Actual Results:  
same as described above

Expected Results:  
It would be nice to see the actual URL

Comment 1

15 years ago
reporter, is firebird open, closed, or either when this happens?
(Reporter)

Comment 2

15 years ago
When it is open.  I actually get another funky error from Thunderbird if I click
there if it is not open as Moz seems to think it should try in Thunderbird first.  

In Mozilla 1.5b I am not having any issues...

Comment 3

15 years ago
sounds like this might related to or same as bug 206936.  reporter, is the theme
for this new window messed up as well?
(Reporter)

Comment 4

15 years ago
Indeed the theme is messed up.  It changes from the default Firebird theme to
the classic Mozilla theme...

Updated

15 years ago
QA Contact: asa

Comment 5

14 years ago
I assume this is fixed now? It's working for me now that the external links bug
is fixed and I can test it out. 20031027 Firebird/0.7+

Comment 6

14 years ago
fixed in 0.7.1
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.