User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Q312461) Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040616 Inside a frameset (mydomain.com), I have a source page (other.mydomain.com) with a form that targets the frame on mydomain.com - this works correctly in: IE all vers. Firefox 0.9c Netscape 7.1 Netscape Navigator 4.8 Opera 7.50 This fails with no activity (Submit button does nothing) in: Mozilla 1.7 Firefox 0.9.1 Is this a new security feature that has been rolled into Mozilla? If so, it should give a warning, rather than silently failing. Reproducible: Always Steps to Reproduce: 1. Create a frameset with a cross-domain source, ex: <frameset rows="100,*" frameborder="NO" border="0" framespacing="0"> <frame name="top" scrolling="NO" noresize src="http://other.mydomain.com/top_myform.html" > <frame name="bottom" src="bottom.php"> </frameset> 2. In the 'top_myform.html' page, target 'bottom' in the frameset shown above, ex: <FORM METHOD="post" ACTION="./myformhandler.cgi" TARGET="bottom"> <INPUT TYPE="text" NAME="terms" SIZE=30> <INPUT TYPE="submit" VALUE="Search"> </FORM> 3. Attempt to Submit form in affected browser. Actual Results: Form output is not trasmitted to frameset as expected. Expected Results: Form output should be trasmitted to 'bottom' of frameset as expected.
An actual example of such a site would help a good bit.
Cross-origin targeted form submissions are no longer allowed as they can let evil sites spoof content origins. Fallout from bug 246448. If you enable popups, do you get a new when attempting to submit?
Sample page: http://www.oldradioworld.de/shopd/shopindex.htm Navigation links in left frame do absolutely nothing in 1.7 and FF 0.9.1 (no hint whatsoever for the user, bad!), but apparently work in 1.8a2.
So... shouldn't this security check just be the same as the one for finding named targets (now that we have a reasoanble security check there)? It looks like they differ slightly... jst? danm?
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.