Adobe Reader won't repaint (hangs) after parent element is hidden.




12 years ago
11 years ago


(Reporter: Clint Hall, Unassigned)


1.5.0.x Branch
Windows XP

Firefox Tracking Flags

(Not tracked)


(Whiteboard: CLOSEME 06/27)



12 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20060111 Firefox/

If a PDF is loaded into an IFRAME, and that IFRAME or IFRAME's parent is hidden using CSS and Javascript, the PDF does not repaint when restored.  This also occurs when simply moving it off the screen using absolute positioning.

It also has the appearance of a hung process within that IFRAME, though I can't be sure if it really has or hasn't hung.  The rest of the elements on the page behave normally.

Reproducible: Always

Steps to Reproduce:
1. Load a PDF in an IFRAME.
2. Hide the IFRAME or the IFRAME's parent using display: none, or move it off the screen using "position: absolute" with a severe negative left position.
3. Restore the previous state.

Actual Results:  
The PDF is not longer visible.

Expected Results:  
The PDF should reappear.  This works fine in IE.

I am using the latest version of Adobe Reader.

Comment 1

12 years ago
I have not managed to locate a duplicate for this bug.  Can this bug be confirmed by someone?
Clint Hall, what is Adobe Acrobat Reader's version or Adobe Reader's version?
(Please put it in summary for ease of understanding of problem/searching bug)
See meta Bug 336184 Comment #2 and dependency tree of meta Bug 336184.
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 06/27
Version: unspecified → 1.5.0.x Branch
No response from reporter re: comment 2 & 3 -->INCOMPLETE.
Reporter, if you still see this problem with the latest release of Firefox 2, please reopen this bug. Thanks!
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.