I have just installed this fantastic module in a site which will have to support 3 languages. Unfortunately, there seems to be some sort of interface bug with the items, which makes using the module quite difficult. This is reproducible both in Safari and Firefox.
When I access a page which requires translation, and click on the 'Translate Text' link, the panel opens up on the bottom of the window. No problem there.
Inside the panel, however:
1) the 'search' field gets clipped by the middle grey column (the one that shows the contents of the unstranslated string)
2) in the "Translation to " column, under the usual translation input field - the one where we are supposed to type in the translated string - there seems to be a SECOND input field, about 50% narrower than the top one. I cannot find any documentation about the function of this second field, and it only seems to show up on some pages, and not in others.
3) the buttons ("save translation", "copy source" and "clear") are all sunk halfway out of the window. If I tab to focus on one of the buttons, the entire interface moves up, and half the top tab ("page text", "source", and "translation to ***") gets clipped off.
4) If I type something in the search field, then delete it, the whole interface moves up by about 2 cms/ 1 inch, in order to allow the 'x' button to pop into view. This means that everything moves up by about 2 cms, and everything on the top of the interface get chopped off - including the entire top bar, and the 'closing' button, which totally disappear. It becomes impossible to read any single-line strings that are selected. The only way to get back to the top is to tab into the translation field (the user must TAB, just clicking on the field won't do it).
This is unfortunately reproducible on both Safari and Firefox. Resizing the window makes absolutely no difference to any of the bugs.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | X Button With Something Underneath | 8.36 KB | icouto |
| Interface after deleting search string | 33.82 KB | icouto | |
| Second input field, and clipped buttons | 13.68 KB | icouto | |
| Search field clipped by string display container | 15.35 KB | icouto |
Comments
Comment #1
gábor hojtsyThanks for the report. Some CSS selectors were badly named. This should all be fixed by my latest commit at http://drupal.org/cvs?commit=138880 and will get into a release very soon (today).
Comment #2
icouto commentedGábor, thank you for the fix. I downloaded the dev release from the 09/09/08, and tested it out today. It seems to have fixed points 1 (the search field is no longer clipped) and 4 (interface no longer screwed up after deleting search string). However, issues 2 (the mysterious 2nd input field) and 3 (buttons sunk past the bottom of the window) still remain. I've tested it with both Safari and Firefox, and it's the same on both.
There also seems to be a new little cosmetic 'glitch', visible in Safari. There seems to be some text (?) which is sticking out from *under* the "X" button in the search field - I'm attaching a screenshot, so that you can see it. This is not visible in Firefox - it seems like the buttons in Firefox are bigger by default, and therefore, cover whateve is underneath quite well.
So, I've taken the liberty to re-open the issue.
Please, do keep up the good work! - it's very much appreciated!!!
Comment #3
gábor hojtsyCould you please try to use the module with a clean Drupal core install, and try to reproduce which module adds in the extra input field and possibly other issues, or whether it is there by default. I suspect the additional input field is a result of some other module misbehaving. And your other issues might as well be so.
Comment #4
icouto commentedGábor, as per your request, started with a clean instal of D6, installed l10n client module, and then proceeded to add one by one of my usual modules, to see which one was causing the 'extra field'.
It is the FCKEditor module. If I disable the module, l10n client displays fine. If I enable it, then the FCKEditor adds not just the extra field, but also some info text underneath the translation field, which lets me know how to refer to the field, if I want to turn FCKEditor off for it. I've tried switching off FCKEditor for the field, but nothing happens - the second field still appears, and the instruction text, too.
It seem there is some incompatibility between the l10n client and FCKEditor. Would you be able to get in touch with the maintainers of the module directly, or would you like me to post a separate bug report there, too?
Comment #5
gábor hojtsyWell, if disabling FCKEditor for that field by the id provided by fckeditor does not work, then this is an FCKEditor bug. Recategorized as such.
Comment #6
wwalc commented@icouto: edit the "FCKeditor Global Profile" and in "Visibility settings" add "edit-target" to the list of excluded fields. Let me know if that worked out.
Comment #7
icouto commented@wwalc: yep, that did the trick! Awesome! :-)
Many, many thanks!
Comment #8
gábor hojtsySolved support request then.
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.