Closed
Bug 263616
Opened 20 years ago
Closed 19 years ago
Iframe rendering corruption
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: maxim, Assigned: bugzilla)
References
()
Details
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10 After scrolling the page, the most-frequently-reported bugs iframe renders with some kind of noise on it. Reproducible: Sometimes Steps to Reproduce: 1.Open the page https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox 2.Try to scroll the page near iframe 3.Some times it becomes corrupt. Actual Results: IFRAME rendered with some kind of noise Expected Results: Normal rendering I use WinXP sp2 with nvidia 61.77 driver
| Reporter | ||
Comment 1•20 years ago
|
||
Comment 2•20 years ago
|
||
Iframes are not reloading properly. If you load a page with an IFrame, then edit the page and change the Iframe's url, such as as:- Original IFrame URL http://www.website.com/frameloader.cgi?loadiframe New Iframe URL http://www.website.com/frameloader.cgi?loadiframe2 It will still load the old IFrame, even when viewing source shows the new frame URL. This has been checked and works in IE.
Updated•20 years ago
|
Assignee: bugs → firefox
Component: Web Site → General
QA Contact: firefox.general
Comment 3•20 years ago
|
||
This screen shot capture a rendering problem. The problem get worse after scrolling, but the initial rendering failed too.
Comment 4•20 years ago
|
||
The rendering problem happens everytime on all of the result pages for Travelcaribe dot com. I am using Browser version 1.0 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0). This problem did not occur on that site in the previous version of Firefox.
Comment 5•20 years ago
|
||
I'm running Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 I am also running into this issue, though I notice it happens to me when I've got more than one iframe on the html page. I also agree that it was not a problem when running the previous version of firefox 0.9
Comment 6•20 years ago
|
||
Try putting "position:fixed" in the style of the iframe. That fixed the problem for us.
Comment 7•20 years ago
|
||
I'm running Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a6) Gecko/20050111 and am having a similar iframe rendering issue, which can be seen in this example. The problem appears when the iframe is nested within at least three levels of iframes, the iframe is resized using javascript and the scrollHeight of the iframe's content is larger than roughly 16384.
Comment 8•19 years ago
|
||
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/
Comment 9•19 years ago
|
||
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
You need to log in
before you can comment on or make changes to this bug.
Description
•