206831 - Form target ignored when target window created in onclick javascript

Status: RESOLVED DUPLICATE of bug 174266

(Core :: DOM: Core & HTML, defect)

Description

[Justin Larue]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030522
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030522

When a form submit button has an onclick javascript that opens a new window, and
the form's target is the new window created via that javascript, the form's
action page opens in the same page as the form, rather than in the new window
created by the javascript action.

Reproducible: Always

Steps to Reproduce:
1. Go to example page posted
2. Click SpellCheck

Actual Results:  
Blank new window created; form action page opened in browser window where form
was submitted

Expected Results:  
New window created; form action page opened in said new browser window

Comment 1

[Justin Larue]

Attachment: example/testcase

Comment 2

[Justin Larue]

May or may not be related to bug 166101

Comment 3

[Rainer Bielefeld]

I am not sure whether I understand the problem.
 
On <http://www.kaosol.net/~ziz/formtarget.html> Mozilla/5.0 (Windows; U; Win98;
de-AT; rv:1.4b) Gecko/20030507 shows effects as following:

When I click spellcheck-button, a popup window opens with text "This should be
in a new window".

Results with other Browsers:

NN4.73
opens blank popupwindow (as mozilla), but without text "This should be in a new
window".

OPERA 6  
exactly as mozilla: opens a popup window with text "This should be in a new window".

IE6
exactly as mozilla

So _I_ can not see any problem

Rainer

Comment 4

[Justin Larue]

I apologize, I forgot to mention one critical point: This only happens when
browser.block.target_new_window is set to 'true'.  

As I understand it, setting that preference should not block the ability of a
form action to target an existing window (created by a javascript action, for
instance), but only from the target directly requesting a new window.  If I'm
wrong, forget this bug.  :)

Comment 5

[Jon Henry]

I'm not entirely sure what to make of this behavior. The bug that deals with
this preference's implementation is bug 78037, I went ahead and asked there
whether this was the desired result or not. Hopefully this will be resolved one
way or the other in a few days. Thanks for the report and updates.

Comment 6

[Torben]

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