-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
provide a way to allow individual blocked requests #7
Comments
This could also fulfill a similar user request of being able to see what was blocked for each destination. (Thanks James Bradwell for the request and for [attachment:view-blocked-items-menu-option.png this mockup].) |
Is this a request for full URI specificity? The attached mockup seems to further segregate the policy settings. Perhaps #100 and single menuitem to a single dialog "ALL blocked items on page"? Alternately, #74 with full URI specificity? |
If possible, I'd like to see this not just configurable through the menu, but via clicking on placeholder elements (e.g. the placeholder images) -- similar to how NoScript lets you selectively permit individual flash items for domains that haven't been whitelisted. |
Replying to [comment:4 4qMPV8HA]:
This feature request was also emailed to me by a user, so I've opened #129 it. |
There should be a way to allow individual blocked requests rather than having to allow an entire domain.
Possibly this could go in an "Advanced" submenu off of the main menu (maybe put it where "Request Log" is and stick "Request Log" under "Advanced", as well). Another option would be to add a new submenu to each blocked/allowed destination and under there list the specific blocked/allowed requests. This starts to get complicated on the implementation side due to the way RequestPolicy tracks blocked and allowed requests for generating the menu: that is, not analyzing the DOM (well, only a little) and instead keeping track of requests that the browser tries to make and associating them with the url of the current page. The risk of misleading info increases a lot if RequestPolicy is stating what the individual items on the page are without looking at the DOM. So, RequestPolicy would need to look through the DOM very thoroughly.
(Thanks to RSnake for the suggestion.)
The text was updated successfully, but these errors were encountered: