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.
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.
Fixed, but apparently not yet released:
http://code.google.com/p/chromium/issues/detail?id=30760#c16
Related
I tried both npapi and firebreath, but all of them only work well on Firefox, and easily stuck on Chrome . the function I wrote in plugin is the simplist "return 0;". i processed the Xemd case.
NPError NPP_GetValue(NPP instance, NPPVariable variable, void *value)
{
...
switch (variable) {
case NPPVpluginNeedsXEmbed:
*((BOOL*)value) = TRUE;
...
}
I'm not sure what versions you are using; Chrome discontinued support for NPAPI plugins (supported by FireBreath 1) in 2014; Firefox discontinued support for NPAPI plugins in Firefox 52, though I believe there was a LTS version of firefox 52 which continued to support them for another year and a half (which is likely over by now).
In short, NPAPI is pretty much dead -- the last holdout in generally used browsers is Safari and it's going away with the release of macOS Mojave.
There is a way to write a firebreath 2 plugin and make it work via native messaging but it's a bit of a complicated process and it's not super well documented; you can find information on the firebreath-dev google group and ask clarifying questions there.
Problem solved when I tried with chrome version 22. Higher version may also work.
It's not easy to find such an old version ,I'm afraid my plugin will never be used.-_-||
So I've just got started with polymer and got this message:
[Deprecation] Styling master document from stylesheets defined in HTML Imports
is deprecated, and is planned to be removed in M65, around March 2018. Please
refer to ....... for possible migration paths.
After doing some reading it seems to be that
<link rel="import" href="/SOR/bower_components/paper-input/paper-input.html">
Was causing the issue and rel=import for html was being deprecated. Is this right? If so what is the fix, how should I be doing this?
Cheers
So, according to the new version of chrome (61.xx.x). Google has made a decision that Styling master document from stylesheets defined in HTML Imports
is not a good approach and so it will be unable to do in future chrome versions.
Because of this, we have to upgrade to version 2.x
Well, nothing much interesting except that Google has made a decision that HTML imports will be removed in future. This is much more frustrating. Everyone who is using Polymer 1.x or 2.x will have to update their projects to newer version of polymer (at least 3.x). Unfortunately version 3.x has no support in all major browsers (except Chrome, but not fully). So we can only hope that the remove of HTML imports will not be soon.
For me this is really piece of s**t. I have many projects written in Polymer and I am not able to upgrade them. (there is no time for this) even i had time, I don't have trust in Google Polymer... Their support is 0. They don't even answer to bugs. Old versions are already stopped from updating. No long-term support versions.
official discussion: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/VZraFwqnp9Y/discussion
The issue has actually been solved by the polymer team, as described on their blog
So versions 1.10.1 or newer for 1.x and 2.1.1 or newer for 2.x are ok, however the warning doesn't go away (see blog entry for more details).
I also tested a polymer 2.6 app on Chromium 65 and on chrome 67 beta and it works fine everywhere :)
If you are using Google Polymer it's worth remembering that webcomponents.js is actually a polyfill. We currently run Polymer version 0.5 and this can actually be tested by starting your current Chrome with those features disabled. On Mac you can do this quitting Chrome and then run from command line:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --disable-blink-features=ShadowDOMV0,CustomElementsV0,HTMLImports
Polymer 0.5 applies the Polyfill when these features are disabled.
Here is the documentation on running Chrome in debug mode Chromium debug flags
I am developing my first extension for Chrome and as I am working on Ubuntu, I've encountered two awful bugs.
The first thing is that chrome.i18n.getUILanguage is not supported! (console gives me an error about unsupported method). The thing is that this problem is not listed on any WIKI page, which may become tricky for beginners. Anyone had similar issue? For now, I am using window.navigator.language.
The second bug is about rich notifications that are not supported (anyone knows when it will be released?). As far as I know, when the app will be about to send a notification, the scripts will stop due to the error (similar to the first bug). I am not sure if there is possibility to develop different packages for different platforms, but if I want my extension to be truly multi-platform, I will have to give up development of this feature.
Any suggestions or thoughts?
Thanks,
As i said earlier in a comment, it seems to be not supported with linux mint either where i'm developing the chrome extension.
In this link a member of the chrome team said that they submitted it... but this is not true.
Thanks for the window.navigator.language alternative.
Is this possible? I think I may have missed something obvious here. I have a live UI scripts app, and I need to fix a bug. The potential bugfix has to be tested on multiple browsers, so it actually has to be published, instead of just trying out the "current version". This means that it has to be published to a new URL.
Thanks.
it actually has to be published, instead of just trying out the "current version" ?
There is no reason why using different browsers should prevent from using de 'dev' version of an app... you can login in many browser at the same time and play with the dev version on each browser (I do that very often using a couple of android and osX browsers simultaneously). Did you try and did you meet issues doing so ?
I need to check a bug in Google Chrome for specific version like 14.0.802.30. How can I get the pervious version for that? Also, how can I switch off automatic update functionailty of Chrome?
Some old Chrome-Versions can be found on oldapps.com if you can't find the version there, you can maybe use the corresponding Chromium release? Its basically Chrome minus the Google-Spyware. For Operating Systems other than linux you have to build your own version tough (easy to follow instructions are published on the website).
Chromium-Releases can be found here