Edit: The bug that caused this problem has been fixed. The @version
tag now works in the stable release. See Issue 30760
Hey.
I've been wondering how I might set the version number displayed for user-scripts in Chrome's extension tab
(source: advefir.com)
So far the obvious methods have failed:
// ==UserScript==
// @version 1.1.5
// @uso:version 1.1.5
// ==/UserScript==
I know Greasemonkey for Firefox doesn't use a version value, but since Chrome actually displays a version number, I thought it might.
Perhaps this is a feature that has not been implemented?
Or maybe it was never intended to be there, but it is there because extensions have version numbers, and user-scripts are currently installed as extensions?
(I'm using the Linux beta, version: 4.0.249.43, by the way)
Thanks.
To get started, install Tampermonkey. Tap its toolbar icon, and select Add a new script . An editor opens with a default script. There's a bunch of metadata at the top; fill out the @match field to control where the script will run.
Go to Chromes extensions page, enable the Allow access to file URLs checkbox at the Tampermonkey item, create a file with the file extensions . tamper. js and drag-and-drop it to Chrome.
Ok, this appears to be a confirmed bug now. (Issue 30760)
Seems the standard @version
meta-data is the correct usage, but it has not yet been implemented.
Edit: The @version
tag now works in the stable release of Chromium (and, therefore, Chrome).
Or maybe it was never intended to be there, but it is there because extensions have version numbers, and user-scripts are currently installed as extensions?
I think so.
Version number used for updating extensions. User scripts currently can not update. "Update extensions now" button doesn't work for them.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With