Re: [Tails-ux] Porting DAVE to Web Extensions
|This message is part of the following thread:|
|the complete thread tree sorted by date|
|Uzair Farooq at|
- Chrome: doesn't work - Firefox: doesn't work without DAVE, should work with DAVE - Tor Browser: doesn't work even with DAVE because of: https://labs.riseup.net/code/issues/10686
- Chrome: doesn't work - Firefox: doesn't work without DAVE, works with DAVE - Tor Browser: doesn't work even with DAVE because Tor Browser is amnesic.
1. DAVE downloads the ISO into the sandboxed file system. 2. It verifies the ISO. 3. After the verification succeeds, it asks the user where to save the ISO in the real file system.
- Less UX work and redesign of the web interface. Still, users would be asked where to save their download *after* the download finishes so some details might change. I haven't thought of this much... - Better resume experience *only* when downloads are interrupted by a *network failure* on Firefox and Chrome (not Tor Browser): - The resume experience is not better than option B when the *browser is restarted* because with this API we're in a virtual file system only in memory so I understand that it's lost when the browser restarts. - When people want to *pause and resume manually* we're not offering more possibility that the vanilla download. Still, we might be able to provide a slightly better UX for Firefox where this feature is harder to find.
- We're downloading in memory so users need ~1GB of RAM to download. - We're downloading in memory and don't really know how browsers behave with ~1GB in memory. - The UX of downloading might be weird if everything happens in a sandbox while users expect stuff to happen on their real file system.
- More UX work and more coding work on the web interface: - Redesign the steps of DAVE, removing the download. - Redesign the workflow of the installation scenarios to force people to verify. See . - Worse resume experience when downloads are interrupted by a network failure on Firefox and Chrome (not Tor Browser).