Open Bug 250647 Opened 20 years ago Updated 2 years ago

? site targeting links and form submissions into a frameset created by another site, might have broken something

Categories

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

1.7 Branch
x86
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: les, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1

The error occurrs when I login to the site and am transferred to my "back
office" - another site in a frame.
+++++ HTML from Ctl-u
<frameset rows="0,*" cols="*" border="0" framespacing="0" frameborder="NO">
		<frame src="blank.asp" marginwidth="0" marginheight="0">
		<frame src="http://cyberwize.com/glsi" marginwidth="0" marginheight="0">
</frameset>
++++

I have put the mentionend entry in about:config with no change in the problem.

The problem does NOT reproduce on Mozilla 1.4.2.

Reproducible: Always
Steps to Reproduce:
1.Go to http://glsi.cyberwize.com
2.Login



Actual Results:  
I get a blank screen

The error occurrs when I login to the site and am transferred to my "back
office" - another site in a frame.
+++++ HTML from Ctl-u
<frameset rows="0,*" cols="*" border="0" framespacing="0" frameborder="NO">
		<frame src="blank.asp" marginwidth="0" marginheight="0">
		<frame src="http://cyberwize.com/glsi" marginwidth="0" marginheight="0">
</frameset>
++++

Expected Results:  
Shown the backoffice home page

I am reporting this website as requested in the release note.
I'm not clear on whether adding the entry to about:config was supposed to fix
the problem????
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
Closed: 19 years ago
Resolution: --- → EXPIRED
Status: RESOLVED → UNCONFIRMED
Component: General → DOM
Product: Firefox → Core
Resolution: EXPIRED → ---
Summary: however these changes may cause problems with some sites" I get (I Ihink) the problem mentioned in the release notes "We have made some changes to fix security problems involving one site targeting links and form submissions into a frameset created by ano… → ? site targeting links and form submissions into a frameset created by another site, might have broken something
Version: unspecified → 1.7 Branch
Assignee: bross2 → general
QA Contact: general → ian
Assignee: general → nobody
QA Contact: ian → general
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.
Priority: -- → P5
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.