Trang web này sẽ có chức năng hạn chế trong khi chúng tôi trải qua bảo trì để cải thiện trải nghiệm của bạn. Nếu một bài viết không giải quyết được vấn đề của bạn và bạn muốn đặt câu hỏi, chúng tôi có cộng đồng hỗ trợ của chúng tôi đang chờ để giúp bạn tại @FirefoxSupport trên Twitter và /r/firefox trên Reddit.

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

JPEG attachments do not open in Write window

  • 3 trả lời
  • 2 gặp vấn đề này
  • 1 lượt xem
  • Trả lời mới nhất được viết bởi user1121639

more options

My Windows 10 system is configured to open JPEG attachments with its default program and so is my Thunderbird. JPEG attachments in Thunderbird’s incoming and outgoing message windows open fine but the same attachments do NOT open when they are in the attachment pane of the Write window. I have submitted a bug report # 1330288 on Bugzilla@Mozilla but the respondent (who calls this Write window pane “the attachment bucket in the compose window”) thinks I need support as this is not a bug in Thunderbird but a configuration issue. Any idea you may have on how to fix this issue will be greatly appreciated. Thanks.

My Windows 10 system is configured to open JPEG attachments with its default program and so is my Thunderbird. JPEG attachments in Thunderbird’s incoming and outgoing message windows open fine but the same attachments do NOT open when they are in the attachment pane of the Write window. I have submitted a bug report # 1330288 on Bugzilla@Mozilla but the respondent (who calls this Write window pane “the attachment bucket in the compose window”) thinks I need support as this is not a bug in Thunderbird but a configuration issue. Any idea you may have on how to fix this issue will be greatly appreciated. Thanks.
Đính kèm ảnh chụp màn hình

Tất cả các câu trả lời (3)

more options

You expressed your problem better when you submitted the bug:

"I clicked Write, wrote a message, attached a JPEG file to it, and double-clicked on the attachment file name. Nothing happened."

From your screenshot, I see that you are definitely looking in the right place in the options.

The problem may be that you have "TWINUI" set to deal with JPG files. "TWINUI" is not a particular program, but is "Tablet Windows User Interface". Theoretically, triggering "TWINUI" should trigger Windows to open the default app for whatever type of file it is. Evidently, that is not working quite right for you.

My solution is to replace "TWINUI" in these options with an actual program to open the JPG files.

First I will give a simple way to doing this, and hope that Windows will cooperate.

Click on the words "TWINUI", then choose from the drop-down box, "Use other". This will bring up a box showing the apps/programs on your computer that you can use to open JPG files. You probably want to choose "Windows Photo Viewer", unless you have a better program (I love FastStone Image Viewer). Select the program then click "OK", then "OK" on the options window.

Now quit Thunderbird, then restart it. Hopefully now JPG files will open more consistently. If not, then you may need to also change the default app for opening pictures, in Windows:

Type "Default programs" into Cortana search. Click the search result for "Default program".

Scroll down on the right side until you see "Photo Viewer" and make sure that it is set for "Photos" or "Windows Photo Viewer".

more options

Thanks, Bruce, but the same problem occurred whatever the default program for opening JPEG files was. Happily, the issue seems to have fixed itself, and the JPEG file opens in Photos. Strangely enough, however, if I set Windows Photo Viewer as the default program, the attachment DOES open in the Write window attachment pane, but in Photos rather than in Windows Photo Viewer.

more options

I'm happy that the problem seems to be solved, but ...

Whenever someone says that what I suggest doesn't work, but that "the issue seems to have fixed itself", I am immediately suspicious.