RequestPolicy/requestpolicy — Issue #106: Context Menu does not reflect policy changes until reload (even if auto-reload disabled)
Author: jsamuel
Created: 2011-12-22 04:01:08+00:00
State: open
Labels: extension

Currently, the only way to change cross site request policy without reload is to manually edit the entries (eg through the preferences dialog) or disable auto-reload and use the context menu.

However, if auto-reload is disabled, the context menu does not update to reflect changes, even those changes generated through the context menu itself, until a subsequent manual reload. This can result in an undue burden on the end user, particularly if a site attempts to make cross-site requests to multiple sites, as the user is forced to try to remember all policy changes since reload or explicitly reload the page to see what has changed, which directly contradicts the users intent of disabling auto-reload and may result in inadvertent undesired policy changes.

'''Steps to Reproduce'''
1. Disable auto-reload
2. Visit a site with 1+ blocked cross-site requests
3. Use context menu to allow the request
4. Check the context menu
5. Reload the page
6. Check the context menu

'''Expected Behavior'''
Steps 4 and 6 should both show the request as allowed.

'''Actual Behavior'''
Step 4 (presumed incorrectly) persists showing the request as denied.
Step 6 shows the updated policy.

'''Additional Info'''
The converse (allow -> deny) is likely affected as well.

'''(Presumed) Related bugs'''
#37, #88: Some sites show as both ALLOW & DENY in context menu
#105: Context menu does not update after non-context menu policy changes