
Loading…
Dynamic Filtering, Inline Scripting Reporting Issue #534
I do get the same exact same behavior for both browsers when I submit both to the same exact steps: inline script blocking not reported in the pop UI, but reported in the request log. Did you force a page refresh for Chrome the exact same way you did for Firefox?
Ok. At the time i was testing in Chrome, i had 0.8.5.3. In Fx, it is 0.8.5.6. So, difference in behavior.
Now, i have updated chrome version too, and both behaves the same. (i.e., block is not reflected in popup UI, but reflected in Request Logger).
So this become dup of #502.
Currently a log entry is created whenever a CSP header is added to disable inline scripts. Fix to #502 would require a log entry is created only if CSP header is added and at least one inline script tag is found on the page. And since this would be done after the page has been bound, both the pop UI and request log would report properly.
Ok, Thanks. At the time that defect was logged, inline script is logged in popUI
Hi,
It looks like inline script blocking is not properly reported in both firefox and chrome.
In Firefox, items blocked through inline script, are not reported in popUI, but its reflected in Request logger.
In Chrome, it is vice versa. It is reported in popUI, but not in Request Logger..
Thanks!