Community
Participate
Working Groups
3.7M7 RHEL 5 Start Eclipse with the argument -dir rtl Open Help Make the contents view small enough that a scrollbar is required The tree is not aligned correctly, titles are squashed against the left margin.
Created attachment 194652 [details] Screen Shot
On Windows 7 the tree does not have this problem
The problem shows only when using the embedded browser, an external browser works fine. The problem also exists in Eclipse 3.6.2.
The problem only exists when using specific versions of XULRunner. Version 1.9.2 of XULRunner does not show the problem. See http://www.eclipse.org/swt/faq.php#specifyxulrunner for more information about how to specify the XULRunner version that Eclipse will use.
Grant, how does the XULRunner selection logic work? On my RHEL5 system there are XULRunners at /usr/lib/xulrunner-1.9.2 and usr/lib/xulrunner-1.8.1.13-lwp The 1.8.1.13 version is getting selected by default when I run Eclipse and that is the one which has RTL issues.
The native renderer detection is described in http://www.eclipse.org/swt/faq.php#howdetectmozilla . I assume #1 does not apply here, so it's probably #2 where it finds your xulrunner. #2 uses xulrunner code to detect a xulrunner in the version range 1.8.1.2 - 1.9.x that's registered on the OS. This detection implementation is out of our hands, and it doesn't offer a second choice of native renderer to use if you don't like the first one it gives. From what I remember it is not actually spec'd to always return the newest xulrunner if multiple installs are found satisfying the version range criteria, which is why there are separate steps #2 and #3 that do almost the same thing. One thing worth verifying is that your xulrunner 1.9.2 is registered on your OS (maybe only your xulrunner 1.8.1.3 is?). To do this cd to its directory and do: ./xulrunner --register-global (or alternatively: ./xulrunner --register-user)
This is probably going to end up being closed as NOT_ECLIPSE since it works when a good version of XULRunner is specified but I will keep it open for now while I do some further investigation.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
