Bug 502930 - RTL text last line on ContextualHelpButton tooltip leaves an extra empty space before it
Summary: RTL text last line on ContextualHelpButton tooltip leaves an extra empty spac...
Status: CONFIRMED
Alias: None
Product: frameworks-kirigami
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 6.12.0
Platform: Other Linux
: NOR normal
Target Milestone: Not decided
Assignee: kdelibs bugs
URL:
Keywords: rtl
Depends on:
Blocks:
 
Reported: 2025-04-17 12:18 UTC by easy_lad
Modified: 2025-04-17 16:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
the red rectangle shows the extra empty space when hovering over info icon at last line of the text. (36.05 KB, image/png)
2025-04-17 12:18 UTC, easy_lad 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description easy_lad 2025-04-17 12:18:06 UTC 
Created attachment 180350 [details]
the red rectangle shows the extra empty space when hovering over info icon at last line of the text.

SUMMARY

RTL text last line on info icon (when hovering over) leaves an extra empty space before it, see image attached, the red rectangle shows the empty space. This issue is with all info icons.


STEPS TO REPRODUCE
1. Switch to RTL language
2. Open System Settings / إعدادات النّظام
3.  Go to Workspace section / مساحة العمل
4. Select General behavior / السلوك العام

OBSERVED RESULT

The last line will have some extra empty space before it for some reason.

EXPECTED RESULT

no extra empty space before it.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 41
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Comment 1 Nate Graham 2025-04-17 16:06:29 UTC 
Can reproduce with the ContextualHelpButton instances shown on `LANGUAGE=ar_ar systemsettings kcm_workspace`.

Seems like a general issue with the component; moving to Kirigami.

I see that we're just using a standard ToolTip object though, so if the problem isn't caused by us failing to propagate layoutmirroring properly (or something similar) then it may be an issue in Qt itself.