When browsing through articles using arrow keys in Akregator it takes a couple of seconds for it to move on to next / previous article, making it a unusably sluggish experience. I checked and saw a much earlier bug report for something similar which involved ibus - not relevant in my case, I don't use ibus and it's still going on. Also, this is happening in version 5.5.1 so it's very up-to-date. Please fix this, thx
I have notice the same in akregator since applications 16.12 release.
Also see similar if I use a toolbar button to "advance to next article". This feels like QtWebengine being slow? Or an impact of it's use?
Issue is somewhat better after upgrading Akregator to 5.5.3 - akregator responds faster to article navigating with arrows but still not instantatious as I experience in other readers (e.g. rssowl). Which for me reduces this bug's severity to minor (akregator is no longer unusable but still annoying to use).
I've been Akregator from git master for a little bit now and noticed no delays when navigating using the keyboard shortcuts. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" when you respond, thanks.
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!
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!