Bug in remorse timer

Of course, it's a corner case but it happened to me yesterday.
In my opinion, when you have your finger on remorse timer and alarm is triggered then delete action should be cancelled.

Is it a corner case, or is it actually a bug ? One may argue (regardless of the usecase of remorse here) that when a modal window like the alarm one, or the phone one, appears, the windowing system should emit "pointer leave" for the window it was in before. Is it currently the case ? I don't know, but the symptom of the remorse not being cancelled may highlight that this leave event is not sent. What do you think ?

Sorry, I misunderstood the meaning of corner case. It's a bug.

Remorse was created to protect us before accidental delete. In this case it's not protecting us. Deleting action should be cancelled.

The intended behaviour is that a quick tap on the colourful banner area cancels the deletion. And that a sideways swipe removes the banner and deletes the object. A long-tap on the banner makes the banner move back and forth sideways and show the hint "Swipe to hide", meaning that the banner can be swept away. During the long-tap the remorse timer is paused. Lifting the fingertip up makes the timer proceed. So, in my honest view, if an alarm happens to hit while somebody is long-tapping the remorse banner (for which there should not be any need, really) it is really a rare coincidence. I would consider this problem a corner case, too.

I really do wonder what might happen if you long-tap the 'X'? ;)