SUMMARY When krunner is opened and slides in from the top, at the same time the input cursor and the “Search ...“ text in the input field slide from right to left. After investigation I now know this comes from the default behaviour of a search input widget, which does this when it receives input focus, because it then hides its looking-glass icon. But to me (I set global animation speed rather high, which also means it is not always butter-smooth) it looks like the GUI is still being constructed while the panel slides in. Partly this is because the icon starts vanishing as soon as krunner moves in, which makes the icon—and thus the reason for the animation in the first place—practically imperceptible. What’s your opinion on avoiding this particular animation? Perhaps the focus can be pre-set, or the icon is set only after creating the widget (I don’t know the particulars on how the GUI is constructed). I think it would give an impression of a seemingly faster responding GUI. Cheers. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9
This should be fixed now for Kirigami.SearchField, but I see that PlasmaExtras.SearchField has drifted out of sync with it and probably needs the same fix done there. For components that are mirrored across Kirigami and PlasmaExtras (PlaceholderMessage, ActionTextField, SearchField, PasswordField) we need to make sure we're applying any changes made to both, until the time when we can delete the PlasmaExtras versions and use Kirigami visual components in Plasma and have the styling work properly.
To the best of my knowledge, the patch in Kirigami got reverted. I had no idea about Plasma counterpart, which is totally my bad. The trick with disabling Behavior components that David merged didn't really work for two reasons: a) code in that patch was querying Window attached property on a wrong object, so it couldn't possibly work as intended; b) even when querying the right object it would simply not work, due the dynamic and non-deterministic nature of signal propagation (and property evaluation), so animation Behavior was getting enabled back before the focus is given, so it just animated anyway. TL;DR a different approach based on imperative code hooked up to a window lifecycle is required to make it work. Meanwhile, revert plasma as well.
Forward-duping to Bug 472391 since that bug report has an open merge request to resolve it. *** This bug has been marked as a duplicate of bug 472391 ***