For TB, better than 1.3, but... Puntuado con 2 de 5 estrellas

Just tried 1.4.2 on TB (same system as in my previous comment).
It translates words and phrases, and the tanslation window does close now, but after that, there's still the transparent screen with all those "victory gestures".
Therefore, in the same message, I cannot perform another translation without closing and opening the entire message again.

For FF, great as always, though.

Using the statusbar icon, everything is ok (just a little bit uncomfortable, since it's far away on a widescreen).
That's why I tried the context menu.
Please, try this:
Mark a word or text and right-click it.
Use the context option to translate.
Then close the popup (doesn't matter, if you use the x button or if you just click somewhere on the screen).
Now, the popup is gone, but not its background with those "victory gestures" (sorry, don't know what you call this officially).

I forgot to mention, did you notice already, if you check or uncheck the option "active" in the menu of the statusbar icon, nothing is happening in TB. Seems to work in FF only.

Esta valoración es de una versión anterior del complemento (1.4.2).  Este usuario tiene otras valoraciones de este complemento.

Strange, since we can't reproduce this, but it sound very bad.
We tried to select a phrase in the preview-window in the inbox and also if we open a message (in its own window):
- select text
- click once on the icon
- the popup opens
- click on the "x" to close => everything is closed

Can you please check if you are doing something else?
Thanks in advance!

I think I know what the problem is.
I tried to click twice on the icon before the popup is shown and then I can't close the layer correctly.
Is this (double-click instead of one click) maybe also the reason in your case?
If yes, we'll try to catch the double-click.

Just saw your edit...
We have uploaded a new version, where the doubleclick-issue should be fixed. I also can't reproduce what you have described going through the context menu. Hopefully this is also fixed with the same change.
Would be great, if you test the new version.