Show blocked resources

[fhd]

Background

Figuring out which resources a page requests (and which of those get blocked) currently requires debugging the app. That makes debugging filter issues prohibitively difficult.

What to change

Add an activity that shows all the resources that get requested, and the filter that blocked them (if any). Since we really need to conserve memory, this should be disabled per default.

[greiner]

Wouldn't it be more comfortable for filter authors to have that infomation displayed on a computer screen rather than on the phone? Maybe we could stream this data to the computer and display it there using USB debugging. This might also eliminate the need for additional memory to be consumed on the device.

Other benefits of this approach:

• We would see more information at once (independent of screen size).
• At some point we could create a nice GUI for that to make filter creation even easier.
• By writing the filters on the computer and allowing the injection of custom filters via this interface we could eventually streamline the whole process.

[philll]

Apparently, we cannot really ask for greiners approach from users when trying to debug something...

[fhd]

Yeah, doing this via USB is possible, and it'd be pretty convenient for working on filter lists.

However, this issue is about showing blocked resources, and for just that I think doing it in the app is the better option. It's less development effort, it doesn't require the user to install the Android SDK, and it works on the run.

Feel free to create an issue for USB debugging of filters though, I think that'd be nice.

[jennifer247]

spam