Closed Bug 1707520 Opened 4 years ago Closed 4 years ago

Dragging message interrupted with new message notification

Categories

(Thunderbird :: Mail Window Front End, defect)

Thunderbird 89
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 458570

People

(Reporter: msajner, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0

Steps to reproduce:

Start dragging a message from one folder to another.
During the operation, before the message is dropped on destination folder, new message arrives.

Actual results:

Popup notification window is shown.
This interrupts the drag & drop procedure.
The dragged message needs to be grabbed again and dragged and dropped one more time.
I would guess this behaviour is there from very beginning of the product.

Expected results:

The drag and drop procedure should be completed regardless the background events like notifications occur and should not interrupt / cancel that process.

Thank you Marek. Yeah, I believe this is still happening. And yes, it has been known to happen since more than a decade (bug 458570). It's also certainly non-trivial to fix, and with XUL trees on their way out, might be even more of a moving target. Have you seen this on Pop or Imap account?
For now, duping to bug 948082 which looks like the generic catch-all.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Flags: needinfo?(msajner)
Resolution: --- → DUPLICATE

(In reply to Thomas D. (:thomas8) from comment #1)

Thank you Marek. Yeah, I believe this is still happening. And yes, it has been known to happen since more than a decade (bug 458570). It's also certainly non-trivial to fix, and with XUL trees on their way out, might be even more of a moving target. Have you seen this on Pop or Imap account?
For now, duping to bug 948082 which looks like the generic catch-all.

*** This bug has been marked as a duplicate of bug 948082 ***

Yes, it was on IMAP acount in my case. Didn't try with POP.

Flags: needinfo?(msajner)

Thanks Marek. Let's dupe it to IMAP bug 458570 then.

You need to log in before you can comment on or make changes to this bug.