Closed Bug 300275 Opened 19 years ago Closed 3 years ago

transparent iframes don't work in mozilla when run from chrome windows

Categories

(Core :: Web Painting, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: ed, Unassigned)

References

Details

(Whiteboard: DUPEME)

Attachments

(1 file)

11.00 KB, application/octet-stream
Details
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050614 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050614 Firefox/1.0+

The transparent iframe testcase example shows that transparent iframes in xul
work in mozilla unless opened in chrome windows via the -chrome commandline

Reproducible: Always

Steps to Reproduce:
Set up testcase:

1.  Download the tescase files in testapp.zip and unzip to the c:\ directory

2.  Set up as chrome by adding the following line to
<firefox-home>/chrome/installed-chome.txt:
content,install,url,file:///C:/testapp/chrome/content/testapp/

To see the correct results:

1.  Launch Mozilla 

2.  Enter URL chrome://testapp/content/

To see it broken:

1.  Enter from commandline:

firefox.exe -chrome chrome://testapp/content/




Actual Results:  
iframes in the chrome window are behaving differently than those in the regular
browser window, specifically in this case, the transparent iframe functionality
is broken

Expected Results:  
behavior should be identical (ie. the transparent iframes should work)


A test case is attached.  It can be used to see the behavior in mozilla as a
chrome as well as xulrunner as an application (where it also is broken)
Attached file Test case application
*** Bug 300214 has been marked as a duplicate of this bug. ***
Probably because we don't hook up content viewmanagers to chrome.
Assignee: nobody → roc
Component: Layout → Layout: View Rendering
QA Contact: layout → ian
Whiteboard: DUPEME
QA Contact: ian → layout.view-rendering
Component: Layout: View Rendering → Layout: Web Painting

Marking this as Resolved > Incomplete since the last activity on this issue was 16 years ago and it might not be relevant anymore.
Feel free to re-open if the issue is still reproducible on your end in the latest FF versions.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: