Closed
Bug 576261
Opened 15 years ago
Closed 15 years ago
XUL Iframe with type attribute set to content doesn't show referenced document
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect)
Core
Layout: Images, Video, and HTML Frames
Tracking
()
VERIFIED
FIXED
mozilla2.0b2
Tracking | Status | |
---|---|---|
blocking2.0 | --- | beta2+ |
People
(Reporter: daniel, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
1.18 KB,
application/vnd.mozilla.xul+xml
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; WOW64; de-DE; rv:2.0b2pre) Gecko/20100630
When I have a xul iframe in a chrome environment and set the type="content" attribute, the defined src will not be shown. However, the document seems to be loaded and the elements can be accessed and manipulated without any visible change. The page remains blank.
When I don't set a src attribute and set it manually on load of the containing xul document, the content will be shown. If the type attribute is not present, it works.
This is reproducable with the latest XULRunner trunk release.
Reproducible: Always
Reporter | ||
Comment 1•15 years ago
|
||
The testcase shows three iframes with different settings. Each label above the setting will explain the details. For more see source.
Reporter | ||
Updated•15 years ago
|
Keywords: regression
Comment 2•15 years ago
|
||
All three iframes are getting loaded for me with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:2.0b2pre) Gecko/20100701 Minefield/4.0b2pre
Can you please also test in a Minefield build? Could it be only related for Xulrunner builds?
Keywords: regressionwindow-wanted
Version: unspecified → Trunk
Reporter | ||
Comment 3•15 years ago
|
||
This will probably only happen in a chrome environment. I will checkout the latest FF nightly.
Reporter | ||
Comment 4•15 years ago
|
||
Yes, I can confirm this bug in the latest minefield build. It is only visible in chrome environment.
To reproduce it press Control+Shift+J to open the error console. Type the following line in the "Code" field and press evaluate.
window.open("https://bug576261.bugzilla.mozilla.org/attachment.cgi?id=455440","win","chrome")
Comment 5•15 years ago
|
||
Confirmed. Would be great if you would have time to check for the regression range.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 7 → All
Hardware: x86 → All
Updated•15 years ago
|
blocking2.0: --- → ?
Reporter | ||
Comment 6•15 years ago
|
||
Works:
Build identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; WOW64; en-US; rv:1.9.3a6pre) Gecko/20100627 Minefield/3.7a6pre
6b36b6da79bd
Broken:
Build identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; WOW64; en-US; rv:1.9.3a6pre) Gecko/20100628 Minefield/3.7a6pre
9c85f9aaec8c
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6b36b6da79bd&tochange=9c85f9aaec8c
Maybe a regression from bug 574690?
Comment 8•15 years ago
|
||
Sure looks like it to me. Why is that code not checking whether the viewer is the "root" viewer for the xulwindow?
Blocks: 574690
Comment 9•15 years ago
|
||
Should be resolved by the backout in bug 574690. In testing a local build with that patch backed out, everything looks good. Please reopen if this is not the case.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 10•15 years ago
|
||
Thanks Jim. Yes, it's fixed with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; en-US; rv:2.0b2pre) Gecko/20100718 Minefield/4.0b2pre
blocking2.0: ? → beta2+
Updated•6 years ago
|
Product: Core → Core Graveyard
Assignee | ||
Updated•6 years ago
|
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•