Looks like this should point to https://www.chromestatus.com/feature/5718547946799104

Also, make the difference between potentially blocked and blocked scenarios. We will probably need to introduce a separate error string when it actually gets blocked because currently the warning string is written at the time of creating the request and we can only know if its blocked when the request finishes.

If it makes things easier, feel free to log an Error (with a different string) after the warning.

Any updates?

The help link is under review in the same CL as the GET request with the intervention header (BUG= 639401 ). CL: https://codereview.chromium.org/2260303002/

I am planning to work on the error message sometime soon (but also keeping its priority lower since we already see the error message when dev tools shows the blocked resources).

For comment 4, the difference between potentially blocked and actually blocked exists today in the form of dev tools console error mentioning ERR_CACHE_MISS for the script in actually blocked cases following the potentially blocked warning.

So it seems we don't need to add a separate error message.