71160 - Form not displaying results in targetted frame

Status: RESOLVED INVALID

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

Description

[Paul Drummond]

If you go the the Create CV section and either log in or create a new account,
the results page is not displayed in the targetted frame. Confusingly, this
seems to work if you go to the Job Search section.

Is this something to do with info going across domains? Our sites are
constructed in such a way that the CGI lives on one domain with other sites
utilising it. If you go to www.goldensquare.com, which is the 'core' domain,
you'll see that we don't have these problems.

Comment 1

[Konstantin Riabitsev]

Should be "INVALID" -- there is an error in the code. The name of the frame you
target is "mainFrame", while in the <a> links you put "target='mainPanel'",
that's why it opens them in the new window.

Comment 2

[Konstantin Riabitsev]

Btw: if anyone wants testing, use:

Username: moztest
Password: moztest
Surname: Mozishvilli

Comment 3

[Eric Pollmann]

Sadly, There is a frame named "mainPanel" inside of the frame named "mainFrame"
(look at the source of http://www.mediatec.co.uk/contents.html)  Moving bug to
"NEW".  :(

CC'ing the guru of FindFrameWithName (or something like that), Dan!  :)

Comment 4

[Konstantin Riabitsev]

Hmmm... Well, the only reason I didn't really look was that I was seeing the
same behavior in NN4 -- any link in the left frame just opened the new window.
Looks like this is recursive. ;)

Comment 5

[Eric Pollmann]

Oops, this is indeed invalid.

See bug 13871 - we don't allow a frame from one domain to update frames from
another domain.  In this case, when the login form is submitted, the result
comes from another domain:

From the form on page http://www.mediatec.co.uk/addEditCV/control.html:
<FORM METHOD="POST"
ACTION="http://www.goldensquare.com/addEditCV/logIn.taf?_function=list&folder=mediatec/addEditCV">

Solution: Put the pages on the same server.  Alternatively, put the pages
different servers within the same domain, and set document.domain.

Comment 6

[Eric Pollmann]

Thanks for the help Konstantin!  Yep - both Navigator 4.x and Netscape 6 have
this security feature in them.  IE doesn't, which is probably why the page
author didn't notice it...

Comment 7

[Konstantin Riabitsev]

Oh, good. That means I'm not going insane yet... I was creating a local testcase
and couldn't figure why is it that it works for me... :)

Comment 8

[Amarendra Hanumanula]

QA Contact update