RequestPolicy/requestpolicy — Issue #99: Increasing specificity does not show less specific origins until reload
Author: jsamuel
Created: 2011-12-22 05:24:33+00:00
State: open
Labels: extension

Steps to reproduce:

0. Remove Google sites as required from whitelist
1. Set specificity setting to 2nd level domain
2. Visit [http://google.com]
3. Check RP Context menu for listed cross-site requests
4. Change specificity setting to full domain, protocol, & port
5. Check RP Context menu for listed cross-site requests
6. RELOAD
7. Check RP Context menu for listed cross-site requests
8. Change specificity setting to 2nd level domain
9. Check RP Context menu for listed cross-site requests

Expected:

RP retains full domain, protocol, & port information of cross site requests for selective display according to users current specificity setting, without requiring reloading each tab.

Steps 3 & 9 should not show 3rd level domains.
Steps 5 & 7 should show 3rd level domains.

Actual Result:

Step 3 did not show 3rd level domains (as expected).
Step 5 did NOT show 3rd level domains (BUT SHOULD HAVE).
Step 7 showed 3rd level domains (after RELOAD as expected).
Step 9 did not show 3rd level domains (without RELOAD as expected).

Remarks:

Presume this also affects increasing specificity to full domains.

Setting low priority as the scope appears to be limited to first reload after specificity setting increase, despite affecting each open tab separately.