canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
No edit summary |
m (Add section of dnd thoughts.) |
||
| Line 1: | Line 1: | ||
== Drag n Drop in Address book == | |||
I put this list together to enable easier formation of what we need to be able to allow/disallow in address book drag n drop. | |||
{| border=1 valign=top | |||
! From !! To !! Copy? !! Move? !! Reason/Notes | |||
|- | |||
| anything || same place || No || No || Don't really want to be able to create duplicates in this way. | |||
|- | |||
| card in ML || Parent ML || No || No || ditto | |||
|- | |||
| anything || read only directory || No || No || | |||
|- | |||
| mailing list || mailing list || No || No || We don't support nested mailing lists at the moment ([https://bugzilla.mozilla.org/show_bug.cgi?id=40301 bug 40301]) | |||
|- | |||
| card || different AB || Yes || Yes || | |||
|- | |||
| card || mailing list || Yes || No || Cards currently have to exist outside a mailing list for the mailing list to work correctly. | |||
|- | |||
| mailing list || different AB || No || Yes || We require mailing lists to have unique names. Otherwise composition would get confusing. | |||
|- | |||
| card in ML || other ML || Yes || Yes || | |||
|- | |||
| card in ML || other AB || Yes || Yes || | |||
|- | |||
| read-only directory item || anywhere || Yes || No || Can't "move" read-only items. | |||
|} | |||
Some other thoughts/concerns: | |||
* DnD code doesn't currently support re-checking for only move or copy allowed - assumes both. Should be an easy fix. | |||
* In cases of card->mailing list and read-only item-> anywhere, "copy" should be the default action. In other cases I think it should be move. I think this can be done within the limits of the existing code. | |||
== Importing Address Book discussion == | == Importing Address Book discussion == | ||