#9 Flashblock breaks when Chrome:// resources are blocked.

I was pulling my hair out when all of my flashblock buttons disappeared. Disabling extensions one by one I found that NRUL was the problem. I'd like to just whitelist the single URI that flashblock needs but not sure which it is.

To find out what to whitelist:

1. In Add-on preferences, toggle Enable Debugging Messages
2. Restart your session. When you notice the problem,
3. Open Developer > Browser Console and find error messages from No Resource URI Leak

Can you help with some example? Because all I see is how to whitelist a DOMAIN so that presumably that domain has full access to all Chrome: and Resource: URIs. What we need is a way to make a specific Chrome: or Resource: available to all, instead of a way to make all available to a specific domain. Or am I understanding this all wrong?

Sorry for ambiguity. "Domains" here refer to what follow "chrome://" or "resource://" so if you whitelist "inspector", all resources from chrome://inspector/ or resource://inspector/ are exposed to all content. (Whether this is good is uncertain. Some Mozilla people are trying to separate a minimum set of exposed resources into special domains so that less information is exposed to content when we block other "normal" domains.)