It started to be happened for some days. I could not click on any tabs on the translation windows.
My OS is Windows 10, I'm using Google Chrome - Version 66.0.3359.181 (Official Build) (64-bit).
Deleting cookies and emptying the cache constitute the usual remedy in such situations. To get targeted advice and contribute with possible improvements to the Google Translate product, you may consider joining the translate community.
Related
I understand what Canary is. But it's pretty useless if you don't know what beta features are available. So is there a place where this information can be found? I've been googling but can't find anything.
Chrome Canary isn't the Chrome Beta, it's built daily and is the bleeding edge of Chromium development. Writing digested changelogs isn't feasible for daily builds.
You can have a look at every change here:
https://chromium.googlesource.com/chromium/src/
click on the current tag, e.g. 62.0.3168.0 and then on log.
For Chrome Beta, the Chromium Blog is a good resource:
https://blog.chromium.org/
e.g. for Chrome 60 Beta:
https://blog.chromium.org/2017/06/chrome-60-beta-paint-timing-api-css.html
Releases (Stable, Dev, Beta) in more detail:
https://chromereleases.googleblog.com/
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 can't seem to find a clear answer on this anywhere.
How far back is it backwards compatible? Do I have to be concerned about creating multiple versions of the extension?
Thanks
"manifest_version": 2 itself does not cause any incompatibility issues.
But you can easily make a mistake and create an extension which is backwards-incompatible, by using features/APIs which are introduced in Chrome 18 or later (manifest v2 came with Chrome 18).
I suggest to not worry about the old manifest version any more, because only Chrome 17- is affected. As of writing, the current stable version is 23. Hardly anyone is using Chrome 17 any more.
See also
How to upgrade extension to manifest v2 and remain backwards compatible? (Stack Overflow answer)
Tutorial: Migrate to Manifest V2 (Official documentation, apply the tips in the reverse order)
Manifest version 2 extensions have to use "background" instead of "background_page" (and the manifest cannot contain it or Chrome refuses to load the extension), but "background" is not supported in older versions of Chrome. This is the main problem.
The only work around I can think of is to publish multiple versions of your extensions and ask users to download and install the correct version.
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