Feature #10681

DAVE should only propose to "Save File" when opening the download

Added by sajolida 2015-11-27 08:22:30 . Updated 2016-01-13 13:04:08 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Installation
Target version:
Tails_2.0
Start date:
2015-11-27
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
ISO Verification Extension
Deliverable for:

Description

And not propose to open it with the archive manager. This might be possible using MIME types.

During the UX testing, we’ve seen at least two people open the ISO file instead of saving it and then they were lost for the cause…

Subtasks

History

#1 Updated by sajolida 2015-12-17 09:27:00

  • Target version changed from Tails_1.8 to Tails_2.0

#2 Updated by sajolida 2016-01-05 17:47:33

#3 Updated by ma1 2016-01-10 01:00:50

  • Assignee changed from ma1 to sajolida
  • QA Check set to Ready for QA

Should be fixed in 0.2.7rc15, submitted to AMO and updated in last git commit.
When you use our UI, the download now starts right away by asking where to save the file, skipping the Save/Cancel/Open confirmation completely.

#4 Updated by tchou 2016-01-11 21:16:48

  • Assignee changed from sajolida to ma1
  • QA Check changed from Ready for QA to Info Needed

Maybe the user flow would be easier by pre-selectionning the usual default folder ?

#5 Updated by ma1 2016-01-12 23:52:09

  • QA Check changed from Info Needed to Ready for QA

tchou wrote:
> Maybe the user flow would be easier by pre-selectionning the usual default folder ?

It does on all platform/browsers (actually, it even remembers the last folder for downloads from that specific site) except on Tails, which apparently (for privacy reasons, I guess) hides any concept of “default/last download folder” from the browser’s APIs. I’m trying to figure out the best alternate approach…

#6 Updated by tchou 2016-01-13 12:40:36

  • Status changed from Confirmed to Resolved
  • Assignee deleted (ma1)
  • QA Check deleted (Ready for QA)

I think my default “folder” was the “Récemment utilisés” (“last used” maybe) smart section. But if it happends let’s assume that users will know how to select a folder :). So I close it.

#7 Updated by sajolida 2016-01-13 12:49:34

  • Assignee set to tchou
  • QA Check set to Info Needed

Giorgio: I think you shouldn’t worry about the behavior in Tails. Since we confined it with AppArmor, users can only save files in /Tor Browser or/Persistent/Tor Browser and this created quite some glitches like Bug #8917.
Right now, it seems like ~/Tor Browser is the default download directory which is fine.

Tchou: it’s not clear from your last note whether you actually tested and validated this? I also don’t see 0.2.7rc15 on AMO.

#8 Updated by sajolida 2016-01-13 12:55:37

  • Assignee changed from tchou to sajolida
  • QA Check changed from Info Needed to Ready for QA

Now I see 0.2.7rc32 in the development channel so I’ll do the test myself. Sorry for the noise.

#9 Updated by sajolida 2016-01-13 13:04:08

  • Assignee deleted (sajolida)
  • QA Check deleted (Ready for QA)

Tested, it works!