New issue
Advanced search Search tips

Issue 681732 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Lazy requires fail when initiated from DevTools

Project Member Reported by calamity@chromium.org, Jan 17 2017

Issue description

If you set a breakpoint in DevTools in an extension before any chrome.* objects are accessed and then type 'chrome' into the console, you get

(BLESSED_EXTENSION context for eemcgdkfndhakfknompkggombfjjjeno) Lazy require of app.binding did not set the binding field

The uncaught native gets disabled and the whole page is borked.

The easiest repro is to set a breakpoint in the Chrome Bookmark Manager at main.js:8.

Assigning to rdevlin.cronin@ for triage.
 
Status: Assigned (was: Untriaged)
[Extensions Triage] Marking as Assigned.

Sign in to add a comment