google-chrome-devtools

I'm working on a testing suite (implemented as a Chrome extension) that programmatically takes and analyzes heap snapshots with Chrome/Chromium's remote debugging protocol. Because Profiler.* doesn't seem to be part of the public protocol, I'm using this page for reference. Right now, I'm able to take a heap snapshot by calling HeapProfiler.takeHeapSnapshot like in the snippet below. However, when I try calling HeapProfiler.getHeapSnapshot , my callback is completely ignored. var debuggerId = {tabId: sender.tab.id}; chrome.debugger.attach(debuggerId, "1.0", function() { var listener = function

I'm trying to achieve something very trivial: Get a list of elements, and then do something with the innerText of each element. const tweets = await page.$$('.tweet'); From what I can tell, this returns a nodelist, just like the document.querySelectorAll() method in the browser. How do I just loop over it and get what I need? I tried various stuff, like: [...tweets].forEach(tweet => { console.log(tweet.innerText) }); page.$$(): You can use a combination of elementHandle.getProperty() and jsHandle.jsonValue() to obtain the innerText from an ElementHandle obtained with page.$$() : const tweets =

Is it possible to disable the ⌘-[0-9] keyboard shortcuts in Chrome's developer tools? It's frustrating to accidentally hit them when I intend to switch tabs (ex, when I hit ⌘-1 because I want to switch to the first tab, but instead being taken to the developer tools "Elements" panel). Update: This feature has landed in Chrome 28 . Open the devtools. Click on the Gears icon in the bottom-right corner Select the General tab Use the checkbox before "Enable Ctrl + 1-9 shortcut to switch panels" to toggle the preference. This option is found in the bottom-right corner of the Settings -> General tab

I want to create a custom profiler for Javascript as a Chrome DevTools Extension. To do so, I'd have to instrument all Javascript code of a website (parse to AST, inject hooks, generate new source). This should've been easily possible using chrome.devtools.inspectedWindow.reload() and its parameter preprocessorScript described here: https://developer.chrome.com/extensions/devtools_inspectedWindow . Unfortunately, this feature has been removed ( https://bugs.chromium.org/p/chromium/issues/detail?id=438626 ) because nobody was using it. Do you know of any other way I could achieve the same thing