Bug 122245

Summary:	Bookmark menu is not displayed at it correct location on RTL desktops
Product:	[Unmaintained] kdelibs	Reporter:	Diego Iastrubni <cuco3001>
Component:	general	Assignee:	Stephan Kulow <coolo>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Favorites menu opened with the mouse The Favorites menu opened with the mouse

Description Diego Iastrubni 2006-02-18 20:46:40 UTC

Version:            (using KDE KDE 3.5.1)
Installed from:    Compiled From Sources

This bug is an old one, which for some reason, was not reported until now. I can remember it, in old versions like 3.2.X. Still valid for KDE 3.5.1 and Qt 3.3.2.

On the attached screen shots, you can see that on RTL desktops the Bookmark pop-menu is not opened bellow the "Bookmark" menu-text. I showed this on kate, but it can be seen in Konqeuror and probably other applications.

The first shoot, was taken after I opened the Bookmark menu with the mouse.
The secondshoot, was taken after I opened the Bookmark menu with the keyboard, by pressing Alt and then navigating with the arrows until I reach the correct menu.

I filled this under kdelibs, since IMHO, the problem is with the code that generates the Bookmark menu and not with kate or Konqueror.

Comment 1 Diego Iastrubni 2006-02-18 20:48:56 UTC

Created attachment 14762 [details]
Favorites menu opened with the mouse

As you see the menu is not in his correct location.

Comment 2 Diego Iastrubni 2006-02-18 20:50:57 UTC

Created attachment 14763 [details]
The Favorites menu opened with the mouse

Same problem - now the menu is on the other side. Now the menu has been opened
with the keyboard.

Comment 3 Diego Iastrubni 2008-08-13 08:58:27 UTC

I traced this bug to a Qt (3 and 4!!!!) bug. It's documented "upstream", at 

http://trolltech.com/developer/task-tracker/index_html?id=222757&method=entry

So safe to close as it's "not our problem" and I don't think there is a workaround available.