InformAction Forums

Hi,

I have issue with Google WordTranslate function in Firefox for a while. I recently read a forum talking about only install Google Toolbar with NoScript work okay. So I try to install the add-on one by one to see the behaviors. I found that once I install Download Statusbar then the Google WordTranslate will stop working. Here is the procedure I did:

1. Install FF 3.6.8
2. install Xmarks 3.7.8
3. install NoScript 2.0
4. Install Google Toolbar for Firefox 7.1.20100723W
5. install IE Tab Plus 1.92.20100607, ScrapBook 1.3.7 and New Tong Wen Tang 0.4.0.6
6. install Download Statusbar 0.9.7

Up to step 5 the WordTranslate still working okay. But when I install Download Statusbar the WordTranslate function stop to work. I disable the Download Statusbar or NoScript and it works again. Does anyone experience the same problem?

Thanks!!

I have almost the same problem in my machines, if noscript is enabled, the word traslation don't works, if noscript is disabled, the traslate works fine, this is an screenshot with noscript off:



How i can use noscript and google word traslation at the same time?

My machines are:

Windows 7 ultimate
Firefox 3.6.8
Google Toolbar for Firefox 7.1.20100723W
Noscript 2.0.1

Xubuntu 10.4
Firefox 3.6.8
Google Toolbar for Firefox 7.1.20100723L
Noscript 2.0.1

PD. Sorry for my poor english.


Regards

Nobody read this posts?
The noscript version is now the 2.0.2.3 but the problem is still there. We are many users that have the google toolbar and noscript, is a shame can't use both at the same time.

Regards

If you try searching, you might see this: http://forums.informaction.com/viewtopi ... 64&p=19351 which should hopefully answer your question. And if not then we can see if Giorgio can take a look and see what's up if its something new or beyond what has already been discussed.

GµårÐïåñ wrote:If you try searching, you might see this: http://forums.informaction.com/viewtopi ... 64&p=19351 which should hopefully answer your question. And if not then we can see if Giorgio can take a look and see what's up if its something new or beyond what has already been discussed.

I had the same issue from a lot, and I had to say it is very annoying...
Surfing the web I understood this happenning because of big G changed something in the way WordTranslate works (more or less, now the popping up translation is not more plain text only, but it also get an imagine and God-only-knows-what something else!).

The above didn't solved the problem, as well as a bunch of attempt playing with Noscript options I made by myself.
I read and tried this and this and more.
The only (let's say so) "workaround" found is... disabling Noscript! That is what i DO NOT want!

Hoping someone can solve that matter asap, as I can't give up having neither WT nor NS...

There is another "workaround": If you add "file://" to the whitelist, it works again also.

But I don't want to add this to the whitelist, because I don't know, how this affects security.


This reminds me of a similar issue a few weeks or months ago:
All of a sudden the history and suggestions of google-toolbar stopped working.
It turned out that adding "file://" to the whitelist solved it, but I didn't want to add it, so I waited a long time and finally Google solved the problem.

Now it seems that google screwed up again!

I'm soooo tired!!!

Can't Giorgio do anything?
I'm afraid Google will need for ever to fix this, if ever.

Thank you
Clavi

Clavi;Re wrote:There is another "workaround": If you add "file://" to the whitelist, it works again also.

That's true Clavi, it works (rebooting Firefox after adding)!

Afaik, "file://" is something related to web local files (I mean: web pages, swf, and so on saved onto HDD; try to open one of these files in Firefox, and you will see the chance to "permits file //" in Noscript permission window).
Nevertheless, permitting "file //" by clicking Noscript related button is not enough to allow WordTranslate to work: you need to reboot Firefox (or adding "file://" to the whitelist and rebooting Firefox).
It means that "temporarily permits file //" cannot be used as a (maybe little bit safer) workaround for WordTranslate...

But I don't want to add this to the whitelist, because I don't know, how this affects security.

Quote!I also don't know _exactly_ how this could affect security, so I'm very reluctant to use this workaround...
Nobody knows something more about "file //" matter?

Can't Giorgio do anything?

Yep! Please, Giorgio: help us!

file:// is used to control how the LOCAL files are being handled by the browser. I don't see how that would be a fix or why it should be necessary but use it with caution. There is a reason why its not in the default list. You can limit your exposure by allowing a SPECIFIC local path like file://to/the/file/needed.extension to limit exposure to a specific item rather than ALL but still we need to know WHY that works and why it should be necessary at all. This could have something to do with locally installed Google applications that may need to run a quasi server to work and can be accessed using file:// but again if you don't have such things installed, then the file:// making it work seems odd. Even IE who is liberal with settings and safety, doesn't allow local content access by default, you have to set it specifically using Internet Options, so you have to realize that its a big issue. When you allow this, all a malicious vector has to do is to have the file cached or downloaded to your drive and then run it and get you that way instead of a direct injection at the website interface.