What steps will reproduce the problem?
0. enable click to script
1. Install the honey extension
2. visit a site with cross-origin iframes (like anything with google ads)
3. allow the extension to always run on that site
4. refresh the page
What is the expected result?
The extension should not appear blocked
What happens instead of that?
The extension appears blocked
This happens because we don't grant subframe permissions with activeTab-style granting. This is currently WAI, and for content scripts, we don't consider this blocking. Webrequest should do the same, where we only surface the webRequest blocked indication in the case of a top frame.
Comment 1 by bugdroid1@chromium.org
, Oct 31 2016