Bug 480241 - Auto-complete needlessly obscures text cursor
Summary: Auto-complete needlessly obscures text cursor
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: 23.08.4
Platform: Flatpak Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-23 19:05 UTC by Ellie
Modified: 2024-03-20 18:05 UTC (History)
3 users (show)

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


Attachments
Video showing the bad autocomplete popup placement (114.34 KB, video/webm)
2024-01-23 19:05 UTC, Ellie
Details
Screenshotg of menus being somewhere randomly on the screen (211.03 KB, image/png)
2024-01-24 17:12 UTC, Ellie
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ellie 2024-01-23 19:05:29 UTC
Created attachment 165166 [details]
Video showing the bad autocomplete popup placement

SUMMARY

When using auto-complete, despite plenty free screen space, the auto-complete overlay often overlays the text cursor itself, making it impossible to see what I'm typing. Maybe it's just me, but this feels somewhat disruptive.

STEPS TO REPRODUCE

1. Type with auto-complete turned on

OBSERVED RESULT

See attached video. Auto-complete pop-up covers text cursor itself with no need. Unless the screen was very cramped and the auto-complete list very long (but even then, maybe it should just be shortened then unless the screen is so small that it doesn't fix it anymore) it shouldn't overlay where I'm typing.

EXPECTED RESULT

I can see what I'm typing, even when auto-complete is enabled, unless the screen really is tiny and it's not reasonably avoidable.

SOFTWARE/OS VERSIONS

Windows: 
macOS: 
Linux/KDE Plasma: openSUSE Slowroll
(available in About System)
KDE Plasma Version: GNOME Shell 45.2
KDE Frameworks Version: 5.114.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
Comment 1 Amir Khan 2024-01-24 16:37:59 UTC
Unable to duplicate on Kate 23.08.4 (same version as your test) on Fedora 39, latest updates applied afternoon of 24 Jan 2024 GMT zone.

I tried this with some Ruby code as I don't know enough Python (yet) and the autocomplete does not obscure the code as in your example. 
I am wondering if there may be an issue with any code/extension that is specific to Python code only?
Comment 2 Amir Khan 2024-01-24 16:43:58 UTC
Unable to duplicate on Kate 24.04.70 on KDENeonDeveloper, latest updates applied afternoon of 23 Jan 2024 GMT zone.

I tried this with some Ruby code as I don't know enough Python (yet) and the autocomplete does not obscure the code as in your example. 
I am wondering if there may be an issue with any code/extension that is specific to Python code only?
Comment 3 Ellie 2024-01-24 16:55:10 UTC
It happens with all file types for me. Other popup menus are also all over the screen sometimes, although I don't know if that's related.
Comment 4 Waqar Ahmed 2024-01-24 17:08:40 UTC
wayland?
Comment 5 Ellie 2024-01-24 17:12:08 UTC
Created attachment 165192 [details]
Screenshotg of menus being somewhere randomly on the screen
Comment 6 Ellie 2024-01-24 18:27:27 UTC
Yes this is a Wayland session, and I'm using the flatpak/flathub beta release of kate.
Comment 7 Amir Khan 2024-01-26 15:44:45 UTC
Thanks for the further info, Ellie. I wonder if this is worth trying and reporting back on:

1. Run in an X11 session instead of Wayland. If that fixes it, it's likely Wayland, not Kate/Flatpak. (I tested on Fedora 39, same version of KDE as you reported, but in an X11 session and could not replicate this unwanted behaviour.)
2. If running in X11 session still has same unwanted behaviour, I'd be a little suspicious of the Flatpak version, as I have had trouble replicating the unwanted behaviour on Kate version 24.04.70, vanilla repo install (KDENeon Developer, as previously reported).
Comment 8 Ellie 2024-01-26 17:10:06 UTC
When you say wayland, do you mean gnome-shell then? Since wayland is the protocol and I assume you don't mean protocol bug or something. Since I've seen similar with other Qt apps and their context menus but not GTK ones, my guess would be that it could be a Qt bug if this is related to the context menu placement as well. If it's a separate issue for the autocomplete, then I wouldn't know. As for an X11 session, I actually have no idea how to do that or if that's still shipped at all.
Comment 9 Christoph Cullmann 2024-02-18 17:16:59 UTC
I think that is greatly improved in the new Qt 6 based release and will be need to retried with that.
Comment 10 Amir Khan 2024-02-19 15:28:58 UTC
(In reply to Ellie from comment #8)
> When you say wayland, do you mean gnome-shell then? Since wayland is the
> protocol and I assume you don't mean protocol bug or something. Since I've
> seen similar with other Qt apps and their context menus but not GTK ones, my
> guess would be that it could be a Qt bug if this is related to the context
> menu placement as well. If it's a separate issue for the autocomplete, then
> I wouldn't know. As for an X11 session, I actually have no idea how to do
> that or if that's still shipped at all.

Hi, Ellie.

Apologies for late reply to this. A few points to be clear on. If you're running Gnome Shell, and it defaults to Wayland, the way to run Gnome Shell in an X11 session is as follows. Log out so that you return to the Gnome Shell login screen. When the system is ready to accept your username and password, you should see a settings gear-box icon towards the bottom right of the screen. If you click on it, it should have the option to start Gnome under X11. Select that option before completing login. After you are logged-in, you should be in a position to check if your KDE apps (like kate) work better under X11.
Comment 11 Bug Janitor Service 2024-03-05 03:46:42 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 12 Bug Janitor Service 2024-03-20 03:45:57 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 13 Waqar Ahmed 2024-03-20 18:05:51 UTC
Please try the 24.02 version. The issue should be fixed.