118200 - Links for this test are not correct

Status: VERIFIED FIXED

(www.mozilla.org :: General, defect)

Description

[Jay Farrell]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
BuildID:    20011205

While doing the button-dropdown test for history, the links did not
seem to behave correctly. While the links for go-menu opened a new
browser window, what looked like the same link for this test did not
open a new browser window, which made it unable to complete this test
with the links given. (I used the links for go-menu, and the test worked fine)

Reproducible: Always
Steps to Reproduce:
1. follow the links for test http://www.mozilla.org/quality/browser/front-
end/testcases/history/button-dropdown.html

Actual Results:  No new browser window was opened when you click on the link
(like it did for go-menu)

Expected Results:  The test seems to indicate that this should behave like the 
previous
test (go-menu), but did not.

I saw this issue on both OpenVMS and Linux. As I've stated above, I
was able to complete this test using the links from the previous
test, go-menu, but I was unable to complete this test using the
links given. I assume this is a documentation issue with how the
links were created for the test case.

Comment 1

[Boris Zbarsky [:bzbarsky]]

to website issues

Comment 2

[Claudius Gayle]

slow down boris, this is just a report of a problem with a testcase I wrote for 
history. It's got nothing to do with mozilla.org and probably not the browser 
either. Dawn Endico, I'm sure, could not care less, nor need she be bothered. BZ, 
do you know if there is any standard practice for dealing with such things, 
anyone?

reporter - please just email me with any further concerns. As for the stated 
problem, i don't get it. You click on a few links and then check the browser 
back-button dropdown. you definitely would not want a new window for this test.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Ah.  I had not noticed that it was assigned to you, claudius.  My apologies...

Maybe we should make it clear somewhere that issues with regression tests,
testcases, and the like should be assigned to the QA of the component in question?

Comment 4

[Claudius Gayle]

I think it's okay to simply file a bug against the author of the doc in question
(in this case me).

confirmed. Thanks Jay. I think used a little dirty trick to do that in the other
testcase. I added <base target="fake"> to the head. That should fix it.

Comment 5

[Claudius Gayle]

fix checked in

Comment 6

[Claudius Gayle]

VERIFIED Fixed