Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

T'bird 60.0 ignores its set folder for saving attachments, when "save" is clicked. Why this failure?

  • 1 Mbohovái
  • 1 oguereko ko apañuái
  • 3 Hecha
  • Mbohovái ipaháva Wayne Mery

more options

In tools | options | attachments Tbird 60.0 is set to Save attachments to a specific folder via browse / OK. Tbird doesn't do that.

In the main window, with the "from" line selected & the message (partly) visible in the lower third of the window, clicking the "save" button on the lower right does not cause Tbird 60.0 to navigate to the folder set for saving attachments. Instead Tbird 60.0 suggests some random folder recently used by Windows explorer or used during another, very different, far earlier Tbird save.

How can this failure be overcome, and the tools | options | attachments setting be given force?

In tools | options | attachments Tbird 60.0 is set to Save attachments to a specific folder via browse / OK. Tbird doesn't do that. In the main window, with the "from" line selected & the message (partly) visible in the lower third of the window, clicking the "save" button on the lower right does not cause Tbird 60.0 to navigate to the folder set for saving attachments. Instead Tbird 60.0 suggests some random folder recently used by Windows explorer or used during another, very different, far earlier Tbird save. How can this failure be overcome, and the tools | options | attachments setting be given force?

Opaite Mbohovái (1)

more options

offpath said

In tools | options | attachments Tbird 60.0 is set to Save attachments to a specific folder via browse / OK. Tbird doesn't do that.

Are you saying version 52 did not do have this problem?