RequestPolicy/requestpolicy — Issue #235: Consolidate Preference Dialog Origin, Destination, and Origin->Destination Tabs
Author: jsamuel
Created: 2011-12-22 19:01:40+00:00
State: open
Labels: extension

imported trac ticket
created: 2011-06-21 11:52:55
reporter: eibwen

There are three separate tabs for policy rules, depending on whether the origin or destination is specified or any URI is permitted. Each tab is otherwise identical, save that the origin and destination tabs lack the destination and origin columns and inputs respectively.

Consequently, users have to edit policy in three different places depending on the type of policy to be edited. These should be consolidated, such that there is only one place to view and edit all policies.

This could be supported by using the equivalent of the html5 placeholder attribute set to "ANYWHERE" or some more user friendly phrase. Any rule with the placeholder should be treated as an origin only or destination only policy, depending on which input was set to the default. Alternately, use separate radio buttons for origin and destination inputs, eg:

Origin
o Permit Origin Matching: [entry input]
o Permit Destination to ANYWHERE

Destination
o Permit Destination Matching: [entry input]
o Permit Origin to ANYWHERE

And throw an error on ANYWHERE->ANYWHERE, specifying why that's a bad idea, mention temporarily allow requests from site and the global bypass option, perhaps even offering to enable one or both instead.

The radio buttons are probably a cleaner more intuitive approach, but both illustrate the fact that the UI can and should be consolidated.