Created attachment 185185 [details] The first line disappears SUMMARY STEPS TO REPRODUCE 1. I have a file called "smlouva_od_vyplaceni" on my desktop. 2. This depends on icon size and on the resolution of your monitor - on my other monitor, this is triggered with filename half the size, so YMWV (your milage will vary), so just make the filename shorter or longer then needed, the point it it should almost(!) fill one line 3. I start renaming it and type in ".odt" OBSERVED RESULT When I type "t", I get on a new line and instead of the box with renaming expanding, the first line is pushed up into obscurity. EXPECTED RESULT The textfield expands and I see all my filename. It probably touches the same code as https://bugs.kde.org/show_bug.cgi?id=475873 https://bugs.kde.org/show_bug.cgi?id=444147 SOFTWARE/OS VERSIONS Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.16.7-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-1160G7 @ 1.20GHz Memory: 16 GiB of RAM (15,3 GiB usable) Graphics Processor: Intel® Iris® Xe Graphics Manufacturer: LENOVO Product Name: 20UNS02500 System Version: ThinkPad X1 Nano Gen 1
Is the file positioned at a screen edge?
I cannot reproduce the issue when I add more text onto the end of the a filename that's almost the max line length, but not quite.
Created attachment 185232 [details] More general video of the bug No, the icon is in the middle. You do not actually need a text that is almost filling a line. Even for a short filename, as I type and the text overflows a line, it does not expand and stays on the one line, I amde a new video that is visibly in the middle demonstrating this. Weirdly enough, when I paste a string that is two thirds of the line-length twice, the text box correctly expands. I tried all the settings in Desktop>Right click>Icons but it happens under all of them. Has the code doing this been touched since 6.4? I am on Fedora 42, tried with external monitors and without them, not sure what else to try.
The code has been touched quite a bit since Plasma 6.4, yeah. That could explain it. Let's assume it's fixed for Plasma 6.5, and revisit if you can still reproduce the issue after upgrading to that version. Thanks a lot!