289024 - If the word ".bind" is found in a link path, targeting a frame or a new window ("target=_blank") is out of order

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Peter Graessner]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.6) Gecko/20050321 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.6) Gecko/20050321 Firefox/1.0.2

Mysterious: a link with target=_blank (or target=<framename>) does not open the
link in a new window (or in the specified frame), when there is the word ".bind"
in the linked path.
I uploaded a test case for you in URL above
(http://pmhg.net/bugs/firefox-link-bug.htm): there are 2 links, both with
"target=_blank".
Click on "Susanne Deibele" (href-path = "susanne.deibele/index.htm" =>
everything is fine (link will be opened in a new window).
Click on "Robert Binder" (href-path = "robert.binder/index.htm"), and the link
will be opened in the same window, not in a new one).
If you rename the folder "robert.binder" to e.g. "robert.cinder" or only to
"binder" (and rename the relating href-path in the link), then the click on
"Robert Binder" will succeed.
I tried various combinations - I'm nearly sure, that it is the word ".bind"
anywhere in the path (also in the name of the linked html-site), that is the
wretch. Firefox seems to interpret ".bind" in any kind of a manner....

Reproducible: Always

Steps to Reproduce:
1.Open URL above (http://pmhg.net/bugs/firefox-link-bug.htm)
2.Download this html-file and the two subfolders "robert.binder" and
"susanne.deibele" on your local environment for better reproducing the "rename
phenomenon"
3.Open your local copy of "firefox-link-bug.htm" and click on "Robert Binder"
(link won't be opened in a new window, even though specified with "target=_blank")
4.Compare with a click on "Susanne Deibele" - this one opens in a new window.
5.Compare the html codes of the two links => they are equivalent
6.Rename the subfolder "robert.binder" e.g. to "robertbinder" (and rename
equivalently the link specified in the html <a href=..>, then click again ==>
now the link opens in a new window as expected.
Actual Results:  
Click on a link with ".bind" in its path forces the link to be opened in the
same window (even though specified with "target=....."

Expected Results:  
Should open in a new window (or targeted frame)

MS Internet-Explorer does not have this problem.

Comment 1

[:Gavin Sharp [email: [e-mail]]]

Attachment: Testcase

Comment 2

[:Gavin Sharp [email: [e-mail]]]

This can be reproduced in the 1.0.x releases (so the aviary branch), but it
works on the trunk (FF1.1). It therefore must have been fixed since the
releases. Can you confirm that it works in a recent nightly?

It is quite a wacky bug though. :)

Comment 3

[Peter van der Woude [:Peter6]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050403
Firefox/1.0+

WFM

both open in a new window

Comment 4

[Peter Graessner]

(In reply to comment #3)
> Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050403
> Firefox/1.0+
> 
> WFM
> 
> both open in a new window

Hmm - I can always reproduce it .... sorry for this trouble!
Do you need more environment information? Or any other idea?

Comment 5

[:Gavin Sharp [email: [e-mail]]]

> Hmm - I can always reproduce it .... sorry for this trouble!
> Do you need more environment information? Or any other idea?

See comment 2. It works on the trunk, which means it will be fixed for Firefox
1.1. It doesn't work with the 1.0.x releases, but has since been fixed. So
either someone finds a checkin that fixed it and dupes this bug to it, or this
bug gets resolved WORKSFORME.

Comment 6

[Peter Graessner]

Oh sorry, Gavin & Peter - my English is not the very best, so I misunderstood
some words and meanings (e.g. trunk I tranlated to german like "beak" or "car
boot" ;-) and wondered a bit.... also I resolved "aviary branch" as a part of a
zoo ;-)
Don't need a plugin or sth. like that - after hours of own analytics to this bug
I'm happy that you found the reason anyhow, and happy about the super skills of
you all, and happy about the high speed you reacted!!
Even if I don't know, what "WORKSFORME" means, I think, I did right to close
this call with the state "Accept bug => assigned"...

So please best regards to all of your fellows from a blooded firefox fan!
Peter

Comment 7

[Jaime Mitchell (use [e-mail] for email)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050610
Firefox/1.0+ ID:2005061008

WFM

This will be fixed in Firefox 1.1 (as per comment 2)

-> WFM