121187 - drag of message summary line (even without drop) garbles bounding box

Status: VERIFIED FIXED

(Core :: DOM: Copy & Paste and Drag & Drop, defect)

Description

[Pekka Nikander]

In Mail & News window, if I start dragging a message summary line,
e.g. in order to move it to a folder, all the subsequent display
updates get garbled.  It looks like fizzilla's idea of the window bounding
box gets somehow garbled, and it updates only part of the window.  
It doesn't seem to matter whether I finish the drag&drop and actually
move the message or just let it drop back to the mail summary window.
My personal feeling is that in order to gain speed, fizzilla makes it's
drawing window temporarily smaller and then forgets to reset it, or
resets it wrong.  What is really strange is that whenever this happens,
also all other windows show the same buggy behaviour, not only the 
mail&news window.

This seems to be a new bug introduced relatively recently.  
I have been using build 2001122809 for some time, and this bug doesn't
appear in it.  On the other hand, it does appear in 20020116 and 20020118.

For me personally this is a road blocker since I am so used to drag&drop
in handling my mail.  Right now I have no other choice but stick using
the old 20011228 build.

Comment 1

[Sheela Ravindran]

Confirming this behavior on mac os x from 2002-01-18-06 build.
I was able to reproduce this behavior described here

I selected a message from an imap account(202kb with a jpg attachment displayed)
Click and drag the message( while dragging I was able to see the thread pane scroll)
Don't let go without moving the message to any folder.
And the release you will see the results described below.  
This results in unable to view any message at all in that session.  You have to
restart in order to use the application. 

Comment 2

[Sheela Ravindran]

reassigning to navin

Comment 3

[Navin Gupta]

> What is really strange is that whenever this happens,
>also all other windows show the same buggy behaviour, not only the 
> mail&news window.

I doubt this has anything to do with mailnews d&d code.
over to xpApps

Comment 4

[Navin Gupta]

reassigning to the owner

Comment 5

[Benjamin Mucci]

Same under MacOS 8.6 OS -> All.

Comment 6

[Pekka Nikander]

I just verified that this bug is still present in Mac OS X trunk 2002012503.
Furthermore, I am inclined to believe that the bug is still
somehow related to the Mail&News window.  The resulting buggy
bounding box seems to be of the same size than the folder
pane, though not as tall.  Thus, it seems like there is some
code that is activated when you start to drag a message line,
and that code tries to somehow optimize the folder pane display,
but does that wrong and/or fails to reset the bounding box.

Maybe is is so simple that the code attempts to **** a bounding
box to the folder pane, but sets it to the "main" window instead?

Comment 7

[Pekka Nikander]

This bug is still present in 20020128 Mac OS X trunk build.
However, it does not seem to be present in 2002012815 Windows build.
Or at least I couldn't trigger it under W2K.

Comment 8

[Chris Dolan]

*** Bug 121855 has been marked as a duplicate of this bug. ***

Comment 9

[Asa Dotzler [:asa]]

This also messes up the browser. If you do a drag and drop of a bookmark in the
manage bookmarks window while it is on top of the browser window the browser
window gets messed up and only part of the viewport works (the part that was
under the drag and drop I think).  Tested mozilla0.9.8 branch build 01/31

Comment 10

[Asa Dotzler [:asa]]

OK, maybe I'm seeing something different but it's very similar. Any drag and
drop in bookmarks or mailnews threadpane totally hoses the browser viewport or
the mailnews threadpane. After the drag and drop the scrollbars in browser or
threadpane stop working and scrolling with the thumbs produces a seriously
corrupted view.  This affects the trunk as well and requires a browser restart
to make it usable.

Steps to reproduce: 
1. open browser
2. open bookmarks
3. drag and drop a bookmark
4. close bookmarks
5. scroll browser window.
Alternate steps to reproduce:
1. open mail
2. drag a message to a folder
3. scroll threadpane.

Results, painting is totally hosed. Must restart to work around problem.

Comment 11

[Mike Pinkerton (not reading bugmail)]

sounds like a bug i already passed over to smfr for a looksee related to his
port changes. It may also be related to jan varga's outliner drag/drop changes.

Comment 12

[Chris Dolan]

Asa, that's the same that I see (as I reported in bug 121855).  But in my
experience restart is not required to fix.  A maximize-unmaximize cycle fixes
the painting until the next scroll retriggers the glitches.

For me, dragging bookmarks just messed up the "manage bookmarks" pane, not the
main browser pane, but I did quit pretty soon after that so maybe I just missed
the glitches.

Comment 13

[Asa Dotzler [:asa]]

This affects the OS X and classic builds, branch and trunk 01/31

Comment 14

[Jan Varga [:janv]]

sounds like 121968

Comment 15

[Simon Fraser [no longer active]]

*** Bug 121968 has been marked as a duplicate of this bug. ***

Comment 16

[Simon Fraser [no longer active]]

Attachment: Stack for view manager assertion about recursive painting

We have some really pathological call chains during dragging; this stack is an
example. When dragging with double buffering on, I get assertions about
recursive painting from the view manager, which indicates problems.

Comment 17

[Jan Varga [:janv]]

See my comments in the bug 121336 and bug 120299.

Comment 18

[Simon Fraser [no longer active]]

So at least part of this is the open 0.9.9 XP bug 121336. Things are worse on 
Mac, but it's bad everywhere.

Comment 19

[Mike Pinkerton (not reading bugmail)]

ok, this recursion didn't happen before. I think jan's refactoring of the drop
feedback code introduced it.

Comment 20

[Simon Fraser [no longer active]]

Wait up. Mac is way more hosed than the other platforms, and behaves differently 
whether double buffering is on or off. So there is a Mac gfx bug lurking that I 
need to fix.

Comment 21

[Jan Varga [:janv]]

taking

Comment 22

[Asa Dotzler [:asa]]

0.9.8 need hopefully covered by bug 120299

Comment 23

[Jan Varga [:janv]]

fixed along with 120299 (I hope)

Comment 24

[Simon Fraser [no longer active]]

Confirmed.

Comment 25

[Terri Preston]

Verified fixed mac os X build 2002022808