Issue 6565 - Ensure the URL is known for requests we might block

lib/requestBlocker.js

Index: lib/requestBlocker.js
diff --git a/lib/requestBlocker.js b/lib/requestBlocker.js
index 025f152f1ba605d1c5b6a6b98d5924e9654c8b81..ce60334a98e1559c594e99e76c48a7f23bfc64ba 100644
--- a/lib/requestBlocker.js
+++ b/lib/requestBlocker.js
@@ -151,7 +151,7 @@ browser.webRequest.onBeforeRequest.addListener(details =>
   let frame = null;
   if (details.tabId != -1)
   {
-    page = new ext.Page({id: details.tabId});
+    page = new ext.Page({id: details.tabId, url: details.url});

[Sebastian Noack, 2018/04/12 13:27:09]

Shouldn't this be rather the originUrl than the url of this request? But then
again I don't get where the error is comming from, since we fall back to the
originURL anyway, and the code path that touches the page object in
checkWhitelisted() isn't even hit as long as an originUrl is given.

[Sebastian Noack, 2018/04/12 13:38:09]

However, if no originUrl is given these request should be ignored now, by
https://issues.adblockplus.org/ticket/6544. Can you still reproduce the error?

[kzar, 2018/04/13 15:36:37]

Yea, unfortunately I can.

[kzar, 2018/04/13 15:36:37]

Yea, good point. Well since we now know why you couldn't reproduce this to
initially (disabled new tab page) perhaps you could try again to figure out
what's happening? I'd rather not change something that I don't fully understand
in case I'm missing something important.

[Sebastian Noack, 2018/04/14 03:21:26]

How do I get that new tab page?

     frame = ext.getFrame(
       details.tabId,
       // We are looking for the frame that contains the element which