Closed Bug 1763965 Opened 4 years ago Closed 4 years ago

Open attachment menu item does not work

Categories

(Thunderbird :: OS Integration, defect)

Thunderbird 100
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tillotso1, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.75 Safari/537.36 Edg/100.0.1185.36

Steps to reproduce:

version 100.0b1 (64-bit). For an attachment, click the save option and choose open, or right-click attachment name and choose open

Actual results:

Save dialog comes up and file is saved but not opened

Expected results:

attachment should be opened in the default app for the file type

Thanks for using and testing the beta version.

I can't reproduce your issue using Thunderbird 100.0b1 on Windows 10 or Fedora 35 Workstation Linux.

Tested with .txt, .jpg, .pdf, and .wav files using right-click > Open, double-clicking on the attachment and Open from the Save drop-down menu.

Try using Help > Troubleshoot Mode.

Robert, your actual result sounds like something which we have already fixed.
Can you update to TB 100.0b2 and see if the problem still occurs?

  • What do you mean by "click the save option"? Dropdown arrow from Save button far-right of attachment pane header?
  • On which file types does this happen?
  • Can you attach a screenshot of your ≡ > Settings > Files & Attachments section?
Flags: needinfo?(tillotso1)

Also Robert, can you please answer comment 1:

(In reply to WaltS48 [:walts48] from comment #1)

Tested with .txt, .jpg, .pdf, and .wav files using right-click > Open, double-clicking on the attachment and Open from the Save drop-down menu.
Try using Help > Troubleshoot Mode.

Problem still seen with ≡ > Help > Troubleshoot Mode… in TB 100.0b2?

No reply from reporter, and this is WFM on 102.0a1 (2022-05-23) (64-bit), Win10

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Component: Untriaged → OS Integration
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.