fix(alarms): drop an Undo offered while no list could show it
A delete can finish while no list is on screen, such as the app sent home the instant the editor's Delete was tapped. Its Undo is now dropped unshown once it is 30 seconds old, instead of surfacing hours later. Alarms and timers share one UndoSlot for this. A card whose swipe is re-enabled mid-settle still slides home.
This commit is contained in:
1 parent
62da327771
commit
697678b226
13 files changed
+134
-40
No files matched your search
@@ -1756,7 +1756,10 @@ replaces it, and when the screen is left with the snackbar unanswered (another
|
||||
tab, Settings, the app closed): an Undo held back and offered later would
|
||||
restore a snapshot from long ago, out of any context, and over a backup that
|
||||
was restored meanwhile. A rotation is the one exception and shows the snackbar
|
||||
again. It is memory only, so process death drops it too.
|
||||
again. A deletion offered while no list was on screen (the app sent home the
|
||||
instant the editor's Delete was tapped) is dropped unshown if it is more than
|
||||
30 seconds old by the time the list is back. Both lists share this as
|
||||
`UndoSlot`. It is memory only, so process death drops it too.
|
||||
|
||||
The swipe is hand-rolled (`ui/common/SwipeToDelete`) rather than M3's
|
||||
`SwipeToDismissBox`, because the tabs are pages of a `HorizontalPager` and the
|
||||
|
||||
Reference in new issue
Block a user