237200 - Double click PDF attachment, get new window, can't close window

Status: RESOLVED INVALID

(MailNews Core :: Attachments, defect)

Description

[Doug Hockin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040219
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040219

If you double click to open a PDF attachement, the PDF opens in a new
"Acrobat Reader" window.  But you can't (always) close that window, because it
says you are trying to shutdown Acrobat and you have other PDFs open in other
browser windows (which I do).  Have to leave this Acrobat Reader window
open until all other PDF documents in the browser are closed.  

Reproducible: Always
Steps to Reproduce:
1. Have one or more PDF document(s) open in a browser window(s).
2. Receive an email with a PDF attachment.
3. Double click the PDF attachment to open it, a new "Acrobat Reader" window
   with the attachment in it opens.
4. Try to close the Acrobat Reader window.

Actual Results:  
Get an error message saying you can't close this window because you have other
PDFs open in browser windows.

Expected Results:  
Acrobat window should just close and leave the PDF's in the browser alone.


Maybe the PDF attachement should open in a new browser window with the PDF
embedded, rather than a separate Acrobat Reader window?

Comment 1

[Doug Hockin]

I've narrowed down the problem a bit.  It doesn't occur with all PDF
attachements, only those that have extra periods '.' in the filename.  In the
attachment
box, the file name is displayed with the wrong icon, the default Windows icon
rather than the PDF icon, and when the file is doubleclicked it opens in a new
window rather than a Mozilla browser window.  I think Mozilla doesn't detect
that it's a PDF document because of the extra '.' in the file name.  This
problem probably happens with any attachment that has more than one period in
the filename.  Windows has no problem detecting the filetype, as in the new
window it opens the attachment with Acrobat.

Comment 2

[Doug Hockin]

Looks like the problem also happens if the .pdf filename has spaces in it.

Comment 3

[Mike Cowperthwaite]

Which version of Acrobat are you using?
I am not seeing this symptom with Acrobat 4.0, Moz 1.8a2-0610, Windows 2000.
My test PDF file is named "tcpa.why.pdf" -- when I double-click the attachment, 
it opens in the same Acrobat window that was already open for a different file, 
and I can close it without a problem.

Comment 4

[Doug Hockin]

I've just retried it with AdobeReader 6.0 Version 6.0.2 5/18/2004
and Mozilla 1.8a1.  I was wrong, there is no need for filenames
with any special characters.  Here's the procedure to reproduce it.

0. Send yourself two emails each with a .pdf attachment.
1. With no Mozilla windows open (Mozilla is not running), open a Mozilla
Mail/News window.
2. Open one of the mails with the .pdf attachment and double click on the
attachment.  The attachment opens in a new Adobe Reader window (not a Mozilla
window).
3. Open an empty Mozilla Navigator window.
4. Open the other email with the .pdf attachment and double click on the
attachment.  This one opens in a tab (I have tabbed browsing enabled) in the
previously empty Navigator window.
5. Attempt to close the Adobe Reader window with the first .pdf in it.  You get
the message: "Adobe Reader: 
One of more PDF documents are open inside a web browswer.  If you
exit Adobe Reader now, those documents will be closed. Are you sure
you want to exit?"

Seems like this could be fixed if Mail/News fired up a Mozilla window
and put the .pdf there, rather than running a standalone Adobe Reader
to put the .pdf into.  One can close all Navigator tabs/windows that
contain .pdfs with getting this error -- it's the standalone Adobe Reader window
that can't be closed.

Comment 5

[Mike Cowperthwaite]

So I guess that  about:plugins  lists an Acrobat plugin?  Which MIME type is 
associated with it?

What is your "When encountered" setting for that type, under
  Preferences | Navigator | Helper Apps
(assuming the type is also listed there)?

Comment 6

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #4)

> 5. Attempt to close the Adobe Reader window with the first .pdf in it.
>    You get the message: "Adobe Reader: 
>  One of more PDF documents are open inside a web browswer.
>  If you exit Adobe Reader now, those documents will be closed.
>   Are you sure you want to exit?"

This seems to be SPEC of Adobe Reader 6.x.
When standalone Adobe Reader is started before or after PDF is displayed in
Browser's tab,
trying to terminate standalone Adobe Reader always issues the warning message.  
The reason why is that same Adobe Reader process is used for PDF display through
plugin and for standalone Adobe Reader application.
Please note that displaying PDF as external application is same as this
standalone Adobe Reader applicaiton process.
See Bug 204017 Comment #5 for detail of my test.

Comment 7

[Doug Hockin]

> So I guess that  about:plugins  lists an Acrobat plugin?  Which MIME type is 
> associated with it?

application/pdf
"Open these files using the default application"

To repeat my question/suggestion in case it wasn't noticed in the previous post:

Seems like this could be fixed if Mail/News fired up a Mozilla window
and put the .pdf there, rather than running a standalone Adobe Reader
to put the .pdf into.  One can close all Navigator tabs/windows that
contain .pdfs with getting this error -- it's the standalone Adobe Reader window
that can't be closed.

Comment 8

[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 9

[Doug Hockin]

Doesn't really apply anymore with Thunderbird.