Userscript chrome

Author: d | 2025-04-25

★★★★☆ (4.7 / 2210 reviews)

scratch projects for kids

Whale (via Chrome extension or Greasemonkey userscript) Kiwi (via Chrome extension or Greasemonkey userscript) Mozilla Firefox (via Greasemonkey userscript) If you've tested it to

Download adata ssd toolbox 3.0.12

Hijacking a variable with a userscript for Chrome

@resource does not seem to work with file:// on both Firefox 88 and Chrome 90.Add this line for example does not work to access the testme.js// @require file:///projects/kms_tampermonkey/src/experiment/testme.jsThe following is the setting of Tampermonkey securityFirefox: ( Allow scripts to access local files set to @resource or "Allow local files" option does not solve the problem)Chrome: (oddly this does not have "Allow scripts to access local files" option as available in Firefox version of TampermonkeyExpected Behavior ============The window title should be changed to "Testing title: " textActual Behavior ===============The window title didn't change at all as though the javascript is not loaded through @resourceSpecifications ==================Chromium Version 90.0.4430.85Firefox 88OS: (i.e. MacOS Catalina 10.15.7)UserScript ======================// ==UserScript==// @name TEST: Mem// @namespace @description Testing @require// @version 1.0// @author macdevign// @include *// @run-at document-end// @require file:///projects/kms_tampermonkey/src/experiment/testme.js// ====================================// ==/UserScript==]"use strict;";Content of testme.js : Change the document title every 1 secondsetInterval(() => {document.title = "Testing title: " + new Date();}, 1000); Whale (via Chrome extension or Greasemonkey userscript) Kiwi (via Chrome extension or Greasemonkey userscript) Mozilla Firefox (via Greasemonkey userscript) If you've tested it to Whale (via Chrome extension or Greasemonkey userscript) Kiwi (via Chrome extension or Greasemonkey userscript) Mozilla Firefox (via Greasemonkey userscript) If you've tested it to This repo contains the code which runs my Hipchat notification icon. It consists of the following:icon-server - A simple webserver which provides an API which toggles a system tray icon.systemd - A systemd service description which starts the icon server on bootuserscript.js - A tampermonkey userscript which sends messages to the icon server when things change in Hipchat.InstallationMake a separate Chrome instance for hipchat. Install TampermonkeyClone this repo to ~/bin/mine/hipchat-iconRun the following command inside the icon-server directory: openssl req -new -nodes -x509 -subj "/C=AU/ST=Victoria/L=Melbourne/O=ZZ Squareweave/CN=localhost" -days 3650 -keyout server.key -out server.crt -extensions v3_ca -sha256Ensure the paths are correct in hipchat-icon.serviceSymlink hipchat-icon.service to ~/.config/systemd/user/hipchat-icon.service.Run systemctl --user enable ~/.config/systemd/user/hipchat-icon.service.Run systemct start hipchat-icon . You should see an icon in your system tray.Add the server.crt as a CA to your hipchat chrome instance.Install the userscript.js as a tampermonkey userscript. Reload the hipchat tab.Open the network tab on the chrome inspector. Check that communications are going from the userscript to the python web server.Get someone to send you a message. If things go well, the system tray icon should go red. If it doesn't, hopefully you'll get something logged to either

Comments

User3163

@resource does not seem to work with file:// on both Firefox 88 and Chrome 90.Add this line for example does not work to access the testme.js// @require file:///projects/kms_tampermonkey/src/experiment/testme.jsThe following is the setting of Tampermonkey securityFirefox: ( Allow scripts to access local files set to @resource or "Allow local files" option does not solve the problem)Chrome: (oddly this does not have "Allow scripts to access local files" option as available in Firefox version of TampermonkeyExpected Behavior ============The window title should be changed to "Testing title: " textActual Behavior ===============The window title didn't change at all as though the javascript is not loaded through @resourceSpecifications ==================Chromium Version 90.0.4430.85Firefox 88OS: (i.e. MacOS Catalina 10.15.7)UserScript ======================// ==UserScript==// @name TEST: Mem// @namespace @description Testing @require// @version 1.0// @author macdevign// @include *// @run-at document-end// @require file:///projects/kms_tampermonkey/src/experiment/testme.js// ====================================// ==/UserScript==]"use strict;";Content of testme.js : Change the document title every 1 secondsetInterval(() => {document.title = "Testing title: " + new Date();}, 1000);

2025-04-15
User8335

This repo contains the code which runs my Hipchat notification icon. It consists of the following:icon-server - A simple webserver which provides an API which toggles a system tray icon.systemd - A systemd service description which starts the icon server on bootuserscript.js - A tampermonkey userscript which sends messages to the icon server when things change in Hipchat.InstallationMake a separate Chrome instance for hipchat. Install TampermonkeyClone this repo to ~/bin/mine/hipchat-iconRun the following command inside the icon-server directory: openssl req -new -nodes -x509 -subj "/C=AU/ST=Victoria/L=Melbourne/O=ZZ Squareweave/CN=localhost" -days 3650 -keyout server.key -out server.crt -extensions v3_ca -sha256Ensure the paths are correct in hipchat-icon.serviceSymlink hipchat-icon.service to ~/.config/systemd/user/hipchat-icon.service.Run systemctl --user enable ~/.config/systemd/user/hipchat-icon.service.Run systemct start hipchat-icon . You should see an icon in your system tray.Add the server.crt as a CA to your hipchat chrome instance.Install the userscript.js as a tampermonkey userscript. Reload the hipchat tab.Open the network tab on the chrome inspector. Check that communications are going from the userscript to the python web server.Get someone to send you a message. If things go well, the system tray icon should go red. If it doesn't, hopefully you'll get something logged to either

2025-03-28
User6578

Since Google distributed Chrome in version 33, it is not possible anymore to use the custom.css file to set the color of visited links. Is there another possibility for Chrome 33? asked Mar 8, 2014 at 16:00 2 Here's a solution that works for all platform and versions of Chrome.Install the Stylus extension.Right-click the Stylus browser action icon (looks like the letter S in a box) and select "Open styles manager".Click "Write new style".Copy & paste the following into the large text area on the right hand side:a:visited { color: red ! important }Enter a name for the style (on the left hand side, near the top).Click the "Save" button (right below the name).Find a page with visited link, refresh, and you'll see the new color.You can find colors you like here, and use code like rgb(255, 0, 0) in place of redSource answered Feb 18, 2016 at 4:36 Vic JangVic Jang3012 silver badges3 bronze badges 7 The Stylist extension doesn't appear in Chrome webstore anymore. An alternative is the Stylebot extension. If the link doesn't work just go to google chrome webstore and do a search for Stylebot. It's very easy to use and you can change more than just link colors to any site including google. Install the extension, go to Chrome > More tools > extensions > Stylebot > options > styles > Add New Style. Then add a url and some css styling. Here's my css style I use for google.com:the result looks like this for a google search:It's very easy to see now the links I've already visited. answered Feb 21, 2018 at 14:29 You should create a chrome extension. It's not a big deal but more cumbersome than before.To guide you, create a content script extension, use the inject css ability and set the permissions to any site(*://*/*)For further details have a look here: answered Mar 9, 2014 at 10:44 DimDim5,0502 gold badges18 silver badges10 bronze badges 2 If you want to use UserScript (like Tampermonkey) instead of Stylus extension, use this UserScript:// ==UserScript==// @name Match Every Site// @namespace @version 1.1// @description change a visited link// @author You// @match *://*/*// for change CSS// @grant GM_addStyle// ==/UserScript==GM_addStyle ( ` a:link { color: #0f00fb9e ! important } // if you also want to change the color of unvisited links a:visited { color: red ! important }` ); answered Oct 6, 2019 at 16:04 MagTunMagTun1,5685 gold badges28

2025-04-22
User5525

Userscripts are JavaScript files that are executed every time the user loads a Scratch page. They can modify the document’s HTML, add new buttons, customize Scratch editor behavior, and so much more.Similarly to userscripts that you might download for userscript managers like Tampermonkey or Greasemonkey, Scratch Addons userscripts consist of pieces of JavaScript that are executed in the same execution context as the JavaScript code from Scratch itself. In browser extension vocabulary, this execution context is often called the “main world”.Even though Scratch Addons userscripts are part of a browser extension, they cannot access any chrome.* or browser.* APIs. Instead, Scratch Addons offers an addon.* API.Declaring userscripts in the addon manifest Some changes require an extension reload from chrome://extensions to take effect, such as updating the addon manifest file.It’s not necessary to reload the extension when changing the source of an already existing userscript JavaScript file. In those cases, reloading the page is enough.Userscripts are declared inside a “userscripts” array.Each item of the array must have the following properties:"url": the relative URL to a JavaScript file."matches": the list of Scratch pages where the userscript will run. See matches for more information.Example manifest:{ "name": "Copy link to comment button", "description": "Adds a "Copy Link" button to all comments on the website, next to the "Report" button.", "userscripts": [ { "url": "userscript.js", "matches": ["projects", " "profiles", "studios"] } ], "tags": ["community"], "enabledByDefault": false}Creating your first userscript Unlike extension content scripts and Tampermonkey userscripts, you must wrap all of your code inside a module default export:// Example userscriptexport default async function ({ addon, console }) { console.log("Hello, " + await addon.auth.fetchUsername()); console.log("How are you today?");}Remember that JavaScript allows functions to be declared inside other functions, for example:export default async function ({ addon, console }) { async function sayHelloToUser() { console.log("Hello, " + await

2025-03-26

Add Comment