User Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0) Gecko/20110820 Firefox/6.0 SeaMonkey/2.3.1 Build ID: 20110820145925 Steps to reproduce: This bug is a followup to bug #681850. Actual results: Currently, the Data Manager allows the user to add a permission for a new site, but, unless the user realizes that he needs to specify the permission type in the list on the right of the Data Manager, the permission is not actually added. For more details, please see bug #681850. Expected results: The proposal is to change the Data Manager UI to look like this (at the bottom of the right pane): +-------------------+ +---------------+-+ +---------------------+-+ +-----+ | Enter a host name | | Select a type |V| | Select a permission |V| | Add | +-------------------+ +---------------+-+ +---------------------+-+ +-----+ For a discussion, please see bug #681850 comment #4.

Adding the proper dependencies to this bug and CC'ing Kairo.

> Currently, the Data Manager allows the user to add a permission for > a new site Not only new: adding permissions to the existing site is the same. Selecting a permission value is really needed (maybe not in the bottom dialog but by adding a new empty line in the content area with all selects etc).

To be honest, I do not understand the problem. @reporter: Please contribute a problem related step by step instruction containing every key press and every mouse click how to reproduce your problem due to <https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines> (similar to report in Bug 1139273)

(In reply to Rainer Bielefeld from comment #3) > To be honest, I do not understand the problem. The problem is that the Data Manager UI is not exactly intuitive when it comes to adding cookie permissions for a new site. In the current UI, the user has to click on the "*" in the list of sites, type-in the site name, select "cookies" from the list next to it and then click Add (see SetCookies.png). The non-obvious part here is that AFTER doing all that, the user has to go to the top of the screen, uncheck "use default" and choose either to allow cookies permanently or for the sessions (see SetPermission.png). Ideally, the actual type of the cookie permission should be chosen in another drop-down list (see the sketch in comment #0), then click "Add" and nothing else. This would require fewer clicks and less guessing. NOTE: This idea applies to all types of permissions, not just cookies. This implies that the second drop-down list is dynamic and is populated based on the choice in the first drop-down list.