Bug 13810 – HTML FORM TARGET not targeting named window/frame

• Status: RESOLVED
• Resolution: INVALID
• Component: Forms

[Stuart Dodd]

When Targeting an existing frame in a frameset/window the requested action/url opens in a new window instead of the targeted frame/window.

This works correctly in WebKit 419 but not in 522+

We are specifically using a javascript submit which is a multi browser W3C implementation of code. 

when submitting this way no action is taken by Safari using Webkit 522 but works in 419.

[David Kilzer (:ddkilzer)]

Created attachment 14654 [details]
Test case for window

This test case works for me with a local debug build of WebKit r21621 (it submits to the new window).

Stuart, could you post an example that's broken for you, along with a list of steps to reproduce it?  Thanks!

Note that running this example DOES produce the following console output (which I haven't seen before):

ERROR: No parent frame in transitionToCommitted:, FrameLoadTypeInternal
(/path/to/WebKit/WebCore/loader/FrameLoader.cpp:4129 updateHistoryForInternalLoad)

[David Kilzer (:ddkilzer)]

(In reply to comment #1)
> Created an attachment (id=14654) [edit]
> Test case
> 
> This test case works for me with a local debug build of WebKit r21621 (it
> submits to the new window).

NOTE: You must disable "Block Pop-up Windows" for the test to open an initial window (although it seems to work regardless).

[Stuart Dodd]

Created attachment 14698 [details]
Complex Frameset Using JS built Forms Example

This Complex Frameset example uses the concepts we are implementing in the live tool, however it does not highlight the bug i was encountering. I have been struggling to reproduce the bug in a valid test case. will continue to attempt to reproduce the bug as a valid test case failing that i'll see if i can send the offending HTML page that refuses to submit. The case where it is failing is using an internal server and not going out over the www.

[Daniel Bates]

Is the test case "Complex Frameset Using JS built Forms Examples" still valid. I get a Google "Method Not Allowed" error  when I click the "Submit via script" button. I am unclear what you mean by "The return action here should load threesl into the adjacent frame for a form submit and google for a script submit."  I think there is a misspelling in this description. Can you elaborate on this remark? Is this still an issue?

(In reply to comment #3)
> Created an attachment (id=14698) [details]
> Complex Frameset Using JS built Forms Example
> 
> This Complex Frameset example uses the concepts we are implementing in the live
> tool, however it does not highlight the bug i was encountering. I have been
> struggling to reproduce the bug in a valid test case. will continue to attempt
> to reproduce the bug as a valid test case failing that i'll see if i can send
> the offending HTML page that refuses to submit. The case where it is failing is
> using an internal server and not going out over the www.

[Anne van Kesteren]

No response from reporter.