279876 - page opens in wrong target when using parameter with 'tart'

Status: RESOLVED INVALID

(Core :: Layout: Images, Video, and HTML Frames, defect)

Description

[Egon Knapen]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

when there are two frames, one for navigation, one for viewing. A link opens in
the wrong frame when there is a parameter contains the following characters 'tart'.

<a target="viewer" href="page1.htm?dir=startpage>opens in this frame</a>
<a target="viewer" href="page1.htm?dir=stoppage>opens in viewer frame</a>

Reproducible: Always

Steps to Reproduce:
1. create a page with two frames, left is called 'nav' the right one 'viewer'
2. in the left page there is a <a href="" target="viewer">
3. in the href="page.htm?dir=start"
4. click on the item, to open the link in the right page.

Actual Results:  
instead of opening the page in the right frame where it should be opened. It
opens the frame in the current frame.

Expected Results:  
Every link should open in the frame specified. In this case in the right frame

When I'm not directly marked for double, I will put an example on the web tonight.

I'm not sure if the categorie is correct.

Comment 1

[Egon Knapen]

A test case can be found under:

http://217.160.164.215/mozillatest/

the second and the last a-href-tag open in the wrong frame.

Comment 2

[Phil Ringnalda (:philor)]

Worksforme, all five links target the right frame.

Are you using any extensions which might be messing with things they shouldn't?
A problem that only occurs with particular characters in a URI makes me
especially suspicious of Adblock.

Comment 3

[Gérard Talbot]

All 5 links of the attached testcase load accordingly the correct documents in
the frame named "full". Mozilla 1.8b build 2005012606 under XP Pro SP2 here.

WORKSFORME

Comment 4

[OstGote!]

WFM with Firefox 1.0 en-US release and Mozilla 1.8b build 2005012506 on WinNT4.

Comment 5

[Egon Knapen]

That's the second time, I got tricked by those Extensions. I'm sorry to bother
you all, next time I will first deinstall all extensions. I deinstalled two
extensions, and reinstalled them afterwards:

- adblock
- disable targets for downloads

Afterwards the problem didn't occur anymore.

Thanks

Comment 6

[Erik Fabert]

Closing bug per comment 5.