Thanks for the rebase Andrea! I was testing the patch on my machine and the new `nsILoadInfo.requestBlockingReason` is always set to `0` for me. Here is what I am doing: 1) Open DevTools Toolbox and Select the Network panel 2) Load https://googlesamples.github.io/web-fundamentals/fundamentals/security/prevent-mixed-coantent/active-mixed-content.html 3) Check out your system console for logs: I created logs in: - onStartRequest https://searchfox.org/mozilla-central/rev/5c8ea961d04767db723a0a15e3a8f7fbca154129/devtools/server/actors/network-monitor/network-response-listener.js#202 - onStopRequest https://searchfox.org/mozilla-central/rev/5c8ea961d04767db723a0a15e3a8f7fbca154129/devtools/server/actors/network-monitor/network-response-listener.js#320 I did something as follows when logging the value: `console.log(channel.loadInfo.requestBlockingReason);` Does the patch work for you? Or am I doing something wrong? Honza
Bug 1493599 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks for the rebase Andrea! I was testing the patch on my machine and the new `nsILoadInfo.requestBlockingReason` is always set to `0` for me. Here is what I am doing: 1) Open DevTools Toolbox and Select the Network panel 2) Load https://googlesamples.github.io/web-fundamentals/fundamentals/security/prevent-mixed-content/active-mixed-content.html 3) Check out your system console for logs: I created logs in: - onStartRequest https://searchfox.org/mozilla-central/rev/5c8ea961d04767db723a0a15e3a8f7fbca154129/devtools/server/actors/network-monitor/network-response-listener.js#202 - onStopRequest https://searchfox.org/mozilla-central/rev/5c8ea961d04767db723a0a15e3a8f7fbca154129/devtools/server/actors/network-monitor/network-response-listener.js#320 I did something as follows when logging the value: `console.log(channel.loadInfo.requestBlockingReason);` Does the patch work for you? Or am I doing something wrong? Honza