125783 - Drag-n-drop a card to an address book, huge box appears

Status: RESOLVED WORKSFORME

(MailNews Core :: Address Book, defect, P2)

Description

[Ninoschka Baca]

Trunk build 2002-02-14: Mac 9.1, Mac 10.1

Overview: Drag-n-drop a card to another address book and it is not obvious where
the card will be placed since it displays a very large box, instead of just
highlighting the desired address book. 

Steps to reproduce:
1. select a card from the results pane
2. drag-n-drop the card to an address book 

Actual Results: A huge outlined box appears. I place the mouse pointer on the
desired address book but it's still not obvious where the card will be placed.
Let go of the mouse and then check the destination ab and the card is copied.

Expected Results: During a dnd, the desired folder should be highlighted so it
is obvious. 

Additional Information:
- Linux: ok
- Win: ok
- Mac 6.2.1: ok

Comment 1

[Ninoschka Baca]

Marking nsbeta1 because better visual feedback should occur. The way it works
now appears more like a guessing game. 

Comment 2

[(not reading, please use [e-mail] instead)]

this is something we've fixed before for the thread pane, and other outliners.

Comment 3

[Jan Varga [:janv]]

Could someone check it again, I landed a fix for this recently.

Comment 4

[[e-mail] (gone - use [e-mail] instead)]

On 9.2 with the 2002-02-28-08 build, I receive no drop target/addressbook
selection, instead the originator's selection remains a rectangular object the
size of the current outliner row.  

Comment 5

[(not reading, please use [e-mail] instead)]

sounds like there are two issues:

1) the region is too big
2) there isn't any drop feedback.

I think #1 is fixed, but #2 might still be broken on the mac.

Comment 6

[Jean-Francois Ducarroz]

I have fixed the big drag box problem for the mail3Pane window a while ago, you
need to pass a specific rect to the drag function else it will drag the whole
widget!

Comment 7

[Jean-Francois Ducarroz]

see bug 72515 for the drag solution...

Comment 8

[Michael Buckland]

Discussed at Mail News bug mtg with Eng Mktng PjM.  Decided to minus and set to 1.2.

Comment 9

[Michael Buckland]

Discussed at Mail News bug mtg with Eng Mktng PjM.  Decided to minus and set to 1.2.

Comment 10

[Mike Pinkerton (not reading bugmail)]

so we're going to ship machv with this problem? given that we know what the
issue is and how to fix it, this baffles me. it's a big usability problem.
removing minus for re-triage.

Comment 11

[scottputterman]

There are a lot of bugs we know how to fix.  We just don't have time to fix them
all.

Comment 12

[Toms Baugis]

build 20020620 [win2k]

(question - should a file an individual bug on this?)

Summary:
Drag'n'drop interface unclear when dragging card from one book to another

Current Results:
When you drag a card from one to another book, it is copied

Expected:
* card should be moved
or
* mouse cursor should have an '+' in it (which ordinary means "Copy")

Comment 13

[(not reading, please use [e-mail] instead)]

mass re-assign.

Comment 14

[Simon Paquet [:sipaq]]

This bug is targeted at a Mac classic platform/OS, which is no longer supported
by mozilla.org. Please re-target it to another platform/OS if this bug applies
there as well or resolve this bug.

I will resolve this bug as WONTFIX in four weeks if no action has been taken.
To filter this and similar messages out, please filter for "mac_cla_reorg".

Comment 15

[Christopher Taylor]

Attachment: screenshot on tb 1.5b1, as discussed on irc with standard8

standard8 wanted to know what the "big box" looks like on osx. here's a
screenshot, taken with tb 1.5b1

Comment 16

[Mark Banner (:standard8)]

Looks like bug 196967 may be the core version of this bug.

Comment 17

[Mark Banner (:standard8)]

I'm not seeing this with:

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1a2pre) Gecko/2008080710 Shredder/3.0b1pre

As Neil mentioned in bug 196967 we now have support for drag images, so I expect this has just gone away. Therefore WFM on trunk. Wontfix on any other branch per bug 196967.