117722 - DOM Inspector access key conflicts with the Import utility

Status: RESOLVED WONTFIX

(Other Applications :: DOM Inspector, defect)

Description

[[e-mail]]

Tasks/Tooks/Import Utility uses I as its access key so DOM Inspector should use D.

Comment 1

[[e-mail]]

Attachment: Proposed patch

Comment 2

[Boris Zbarsky [:bzbarsky]]

Comment on attachment 63244 [details] [diff] [review]
Proposed patch

r=bzbarsky

Comment 3

[Christopher Aillon (sabbatical, not receiving bugmail)]

Personally disagree with the accesskey chosen.

D should be for debugger which currently has no accesskey.

People will be more apt to call them Inspector and Debugger.  Therefore the
mnemonics should be chosen appropriately.  Either I or N should be the inspector
accesskey and the D should go to Debugger.

Also, why is Import Utility there?  Can we get rid of it?  Or change it's
acceskey to M or U so that Inspector can have I?

Comment 4

[[e-mail]]

Attachment: Patch to remove Tasks/Tools/Import at timeless and caillon's request

Comment 5

[[e-mail]]

Attachment: Patch to remove Tasks/Tools/Import at timeless and caillon's request

Comment 6

[timeless]

jglick: we're going to remove the import utility. users who want to import 
stuff can use file>import in mail.

Comment 7

[jglick]

I have mixed feelings about removing the menu item. 

On the one hand, each component that needs Import/Export has the menu item in 
its File menu already (Address Book, Mail, Manage Bookmarks).

On the other hand, do we want each component to have separate Import/Export 
items? Or would a global type Import tool/wizard, in which users could 
go to one place to Import/Export Address Books, Mail or Bookmarks make sense?

cc'ing Marlon and Lori for their opinion.

Comment 8

[timeless]

jglick: if a tree is removed from the forest and no one complains was it worth 
keeping?

alecf: would you sr= this? at the very least we'd get feedback from the 0.9.8 
release.

Comment 9

[Alec Flett]

why remove it? Why not just fix the access key?

Comment 10

[timeless]

because import exists in file>import. There's no reason to keep an extra copy 
of it at a deeper level.

Comment 11

[jglick]

I'm not saying we shouldn't remove it. That may very well be the right thing to 
do. But I think we need to make sure a broader set of folks are aware of this 
before you remove a menu item.

Yes the menu item appears in several places. But there are two ways to solve 
this. 1) Leave Import/Export in the File menu of each applicable component and 
removed the more hidden global menu item. 2) Make the Global Import/Export menu 
item more obvious and remove all the individual component menu items.

Comment 12

[[e-mail]]

Comment on attachment 63254 [details] [diff] [review]
Patch to remove Tasks/Tools/Import at timeless and caillon's request

Actually the global item is in the wrong overlay so it needs removing anyway.

Comment 13

[Joe Hewitt (gone)]

-> neil

Comment 14

[[e-mail]]

Fixed by the Tools menu reorganization.