12

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

Example image
(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.

Glorfindel
  • 21,988
  • 13
  • 81
  • 109
Atli
  • 7,855
  • 2
  • 30
  • 43

3 Answers3

5

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).

Atli
  • 7,855
  • 2
  • 30
  • 43
1

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.

NVI
  • 14,907
  • 16
  • 65
  • 104
1

Fixed, but apparently not yet released: http://code.google.com/p/chromium/issues/detail?id=30760#c16

none
  • 11
  • 1