ReferenceError: browser is not defined

[Slexom]

Environment

AdBlock version: 3.4.3
Chrome version: 72.0.3626.119
OS: Windows 10, 64-bit

How to reproduce

1. Run a React app in development on localhost
2. Open the chromeDevTool panel
3. Reload the page

Observed behaviour

The debugger pause the page with the following exception.

"ReferenceError: browser is not defined
at eval (eval at shouldWrapAPIs (chrome-extension://cfhdojbkjhnklbpkdaibdccddilifddb/polyfill.js:209:7), <anonymous>:1:1)
at shouldWrapAPIs (chrome-extension://cfhdojbkjhnklbpkdaibdccddilifddb/polyfill.js:209:7)
at chrome-extension://cfhdojbkjhnklbpkdaibdccddilifddb/polyfill.js:218:7"

This issue appeared 2 days ago. Disabling ABP in localhost not solve the problem. In the app I include @babel/polyfill(version 7.2.x, latest version at this moment), can it generate conflicts?

Expected behaviour

No exception is displayed.

[Slexom]

Misclicked without filling requested info.

Environment

AdBlock version: 3.4.3
Chrome version: 72.0.3626.119
OS: Windows 10, 64-bit

[mjethani]

I'm not sure how the error is not getting handled already given that this is what shouldWrapAPIs() looks like:

function shouldWrapAPIs()
{
  try
  {
    return !(browser.storage.local.get([]) instanceof Promise);
  }
  catch (error)
  {
  }

  return true;
}

Is it possible for you to make a standalone React app that we can use to reproduce this issue?

[kzar]

Thanks for taking the time to file this bug report. Please could you clarify a few things?

• When you say to "Run a React app in development on localhost" could you provide a small example project we can use to test with?
• When you say "Open the chromeDevTool panel" do you mean open the Chrome developer tools, or to open the Chrome developer tools and then switch to the Adblock Plus pane?
• You mentioned "AdBlock version: 3.4.3", but later talked about ABP. Are you using the Adblock Plus or AdBlock extension? (If you're using Adblock Plus, are you using the development build, or the standard release?)

[sebastian]

Sorry, but we switched to GitLab. If this issue is still relevant, please file it again in the ​new issue tracker.