Feature #10685
Change in IDF should reset DAVE
0%
Description
The download extension (aka DAVE) keeps it state (“verified” “failed”) until the user trigger its reset with the “Download again” button. Still, whenever the IDF changes, for example to describe a new release or an emergency release, DAVE should reset its state and propose downloading again.
Subtasks
History
#1 Updated by sajolida 2015-11-30 11:15:21
- Priority changed from Normal to Low
Setting this as low priority for the beta. We’ll most probably release an update of DAVE between the beta and the final release. So we can force an upgrade through the “extension-version” field and this should reset the state of the extension. ma1, can you confirm this?
But in the future, we should rather use the “extension-version” field in case of code incompatibility or security upgrade.
#2 Updated by ma1 2015-11-30 11:55:26
Confirmed, upgrading DAVE (but also disabling+reenabling it or reinstalling it) causes it to reload the IDF and reset its state. It also happens if you restart the browser.
#3 Updated by sajolida 2015-12-17 09:26:35
- Target version changed from Tails_1.8 to Tails_2.0
#4 Updated by sajolida 2016-01-05 17:48:02
- Parent task changed from
Feature #8590toFeature #8592
#5 Updated by ma1 2016-01-08 21:16:39
- QA Check set to Ready for QA
Currently the IDF is checked every time the download page is loaded, and the download state reset if a change is detected.
This is the behavior we agreed upon, IIRC. Please let me know otherwise.
#6 Updated by intrigeri 2016-01-09 14:08:52
- Assignee changed from ma1 to sajolida
#7 Updated by sajolida 2016-01-15 14:45:52
- Status changed from Confirmed to Resolved
- Assignee deleted (
sajolida) - Priority changed from Low to Normal
- QA Check deleted (
Ready for QA)
This is working fine now. Congrats!