230508 - when several tabs show a PDF file via the plugger plugin some clients are not swalloed correctly

Status: RESOLVED EXPIRED

(SeaMonkey :: Tabbed Browser, defect)

Description

[Simon Anders]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.5) Gecko/20031007

I'm running Mozilla with the usual 'plugger' plugin and use it frequently to
display PDF files. Plugger will then start an Acrobat Reader and 'swallow' it
into the client area of the browser window. However, if I already have a tab
with a PDF file and point the browser in another tab to another PDF file, things
usually (nearly always) go wrong:

Acrobat reader starts as a stand-alone window which appears in the lower
right-hand corner of the screen -- so low that only the upper left corner of the
window ist visible. The window is not swallowed, but stays there. Sometimes it
even appears without window decoration (i.e. window frame), making it impossible
to manually pull the window into the screen with the mouse.

The phenomenon is nearly always reproducible. I keep observing it, with several
versions of Mozilla, including 1.5, 1.6a, 1.5a and 1.2.1. (I'm not sure but it
might be the case, that it did not occur as regularly with the older versions.)

I'm usually working with Gnome (Gnome v2.0 in the standard configuration of
RedHat 9) and not sure whether the problem also occurs with other window managers.

Reproducible: Sometimes

Steps to Reproduce:

Comment 1

[Boris Zbarsky [:bzbarsky]]

So why is this a mozilla bug and not a plugger one?  We just start plugger; we
don't know anything about the PDF viewer it starts....

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 4

[Simon Anders]

Note added after expiry:

The bug has not accoured to me since quite a while, at least not again since the
release of Firefox. It seems reasonable to assume that it has been fixed en
route recently.

Coonsider it FIXED.