Closed
Bug 550786
Opened 14 years ago
Closed 14 years ago
Problem to display a pdf document in a iftram
Categories
(Core :: General, defect)
Core
General
Tracking
()
RESOLVED
DUPLICATE
of bug 534355
People
(Reporter: garnierludovic, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.5.30729; .NET CLR 3.0.30618) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.2) Gecko/20100115 Firefox/3.6 We developed a software with XUL language. This software is a firefox extension This software enables to display pdf document. Since Firefox 3.6 edition, each time we want to open a pdf document it doesn’t work and a black screen appears, but all other functionalities work properly This malfunction only appears with chrome extensions but don’t appear in a xul file directly called from the navigator. Reproducible: Always Steps to Reproduce: 1.Change iframe source with pdf source 2.Ifram screen becomes black and the pdf document doesn't appear. 3. Actual Results: Black screen appears in the iframe space Expected Results: The pdf document is supposed to be opened properly in the ifram space with a Acrobat Reader plugin.
Comment 1•14 years ago
|
||
Is this a type="content" iframe or a type="chrome" iframe?
(In reply to comment #1) > Is this a type="content" iframe or a type="chrome" iframe? It's an iframe with no type specified. I've tried to change the type but the bug is the same in all cases (chrome or content). The iframes are like <iframe id="myId" flex="1" /> and are placed in a chrome extension.
Comment 3•14 years ago
|
||
For no type specified, you're seeing bug 534355. You also have a security bug if you're doing that. For <iframe type="content">, is that iframe a child of the toplevel XUL document? Or is it a child of some other chrome frame? In the latter case, you're seeing bug 529263 (which will be fixed in the next 1.9.2 update).
I have made a test on pre release firefox 3.6.2 and it was successful. The iframes containing the pdf are without type attribute, and we have to specify it (type="content") to resolve entirely the bug. Thanks a lot for your answers.
Updated•14 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•