RequestPolicy/requestpolicy — Issue #187: Sort the Menu
Author: jsamuel
Created: 2011-12-22 18:58:56+00:00
State: open
Labels: extension

imported trac ticket
created: 2011-02-12 11:47:53
reporter: eibwen

Currently, the menu appears to be sequenced as, if I recall correctly, the (potentially attempted?) cross site requests are detected -- eg via inspection of the src attribute.

This leads to a very interesting menu, eg:

z.example.com
d3.example.org
q.example.com
a1.example.com
v.example.net
b.example.com

This may not matter as much if a user is looking to inspect each entry in turn; however, if a user is looking to find (or inspect) a specific site, the user has to look at every entry. Yet, if the list was sorted, the user can readily identify the desired site, eg:

a1.example.com
b.example.com
d3.example.org
q.example.com
v.example.net
z.example.com

Another possibility would be to sort example.com as a block separate from example.org and example.net.

Further, a simple alphabetic sort may or may not be optimal; however, it is seen as a significant improvement.