It’s the last selected DOM node index. Chrome assigns an index to each DOM node you select. So $0 will always point to the last node you selected, while $1 will point to the node you selected before that. Think of it like a stack of most recently selected nodes. As an example, consider the … Read more
The best thing to do is to install the Tampermonkey extension. This will allow you to easily install Greasemonkey scripts, and to easily manage them. Also it makes it easier to install userscripts directly from sites like OpenUserJS, MonkeyGuts, etc. Finally, it unlocks most all of the GM functionality that you don’t get by installing … Read more
Follow these easy steps! Press Command+Option+i (Ctrl+Shift+i on Windows) to open DevTools. Make sure that the developer tools are undocked into a new window. You may have to undock from the menu: Press Command+Option+i again on this new window. That will open the DevTools on the DevTools. You can redock the page’s DevTools if you … Read more
Based on the examples in “Changes to Cross-Origin Requests in Chrome Extension Content Scripts”, I replaced all invocations of fetch with a new method fetchResource, that has a similar API, but delegates the fetch call to the background page: // contentScript.js function fetchResource(input, init) { return new Promise((resolve, reject) => { chrome.runtime.sendMessage({input, init}, messageResponse => … Read more
I believe this is caused by HSTS – see http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security If you have (developed) any other localhost sites which send a HSTS header … e.g. Strict-Transport-Security: max-age=31536000; includeSubDomains; preload … then depending on the value of max-age, future requests to localhost will be required to be served over HTTPS. To get around this, I did … Read more
Good news Chrome dev tools now allows you to save the console output to a file natively Open the console Right-click Select “save as..” Chrome Developer instructions here.
Use chrome.tabs.query() like this: chrome.tabs.query({active: true, lastFocusedWindow: true}, tabs => { let url = tabs[0].url; // use `url` here inside the callback because it’s asynchronous! }); This requires that you request access to the chrome.tabs API in your extension manifest: “permissions”: [ … “tabs” ] It’s important to note that the definition of your “current … Read more
The Chrome CSS property -webkit-print-color-adjust: exact; works appropriately. However, making sure you have the correct CSS for printing can often be tricky. Several things can be done to avoid the difficulties you are having. First, separate all your print CSS from your screen CSS. This is done via the @media print and @media screen. Often … Read more
In case anyone’s searching for this later on, a nice trick to get rid of those jagged edges on CSS transformations in Chrome is to add the CSS property -webkit-backface-visibility with a value of hidden. In my own tests, this has completely smoothed them out. Hope that helps. -webkit-backface-visibility: hidden;
Note: This answer covers several versions of Chrome, scroll to see v52, v48, v46, v43 and v42 each with their updated changes. Chrome v52+: Open the Developer Tools (Windows: F12 or Ctrl+Shift+I, Mac: Cmd+Opt+I) Click the Customize and control DevTools hamburger menu button and choose More tools > Rendering settings (or Rendering in newer versions). … Read more