Closed Bug 2681 Opened 26 years ago Closed 25 years ago

[Frame layout] Plugin in frame doesn't get redrawn on resize

Categories

(Core :: Layout, defect, P2)

Product:
Core
Component:
Layout
Platform:
x86
Windows 95
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: paulmac, Assigned: paulmac)

References

(
URL
)

Details

DUP of Bugsplat's 94120, will be verified by paulmac once browser and plug-ins are functional. ------------------------------------------------ I know this has been filed already somewhere, but I can't find it now. This is probably related to 94108, and is therefore P1-critical. ------- Additional Comments From byrd 01/06/98 18:35 ------- Here's some info from Adobe: Bug# State: Status: S P Product Version Phase Build Reported B Date Rptd -------- ------ ------------ - - ------------------------- ------- ------------ ------ ---------- ---- 175222 Open ToFix 4 4 Acrobat Browsers 4.0 Beta 3.0 Eastwood 09/23/96 Title: Netscape Navigator - Problems resizing PDF files in frames Description Resizing frames in Navigator does not properly udpate a PDF file being viewed in that frame. DETAILS: Open a PDF in a frame, for example using the HTML code below. Resize the Netscape window. The PDF frame does not resize. Something is getting buggered with the parent window to the PDF window. It does not seem to be getting messages. This can lead to crashes in many instances. <HTML> <FRAMESET COLS="30%,70%"> <FRAME SRC = "toc-simple6n.html" NAME = "tocFrame"> <FRAME SRC = "../test/pdf/simple6n.pdf" NAME = "pdfFrame"> </FRAMESET> </HTML> ------- Additional Comments From byrd 01/06/98 18:56 ------- I'm pretty sure this is due to wfe_ResizeFullPagePlugin not being called in ns/cmd/winfe/cxwin.cpp (line 993). Alex - would you mind testing on Mac to verify that this is WinFE bug? ------- Additional Comments From byrd 01/07/98 12:49 ------- Looks to me like the on the full page (non-framed) case, I keep the same context on a resize. But on a frame, I have a new one, and none of the plugin creation stuff is being called when the new one's created. I imagine this is fixed in the XP tree - perhaps we should check. T'would be nice to therefore postpone this to 5.0, but Adobe and others really want this one fixed. Toshok - any suggestions? Should we make slap a patch on the frame context creation so that it calls the plugin creation? This could cause new issues, related to the plugin's data, reconnect stuff we do, etc.
Status: NEW → ASSIGNED
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Target Milestone: M4 → M5
Target Milestone: M5 → M6
QA Contact: 4144 → 3819
Setting me as QA contact.
Target Milestone: M6 → M8
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.