ngraham added a comment.
In D18798#418056 <https://phabricator.kde.org/D18798#418056>, @pino wrote: > Also, please do not resort to psychological tricks like "torture our users", as if this is any worse than any behaviour issues there. There is no psychological trick. This is simply how I see things: we are doing this for the users. Users are experiencing this bug. We have a known, working, low-risk (or even risk-free) patch that fixes the issue. The patch is a workaround rather than a true fix, but this is because nobody has so far figured out how to fix the issue itself without introducing substantially more risk. Given these conditions, I don't see the harm in landing the patch. Everything in life involves trade-offs, and to me, this patch falls into the category of "don't let the perfect be the enemy of the good." I heartily agree with you on the general principle of avoiding workarounds and fixing issues at their root causes. However so far nobody has been able to do so for this issue. On the other hand, we have a workaround that we already know works and does not cause regressions because we already uses it with success in other places. In this messy world we live in, sometimes workarounds are the lesser evil. The alternative is that this remains broken for users and we continue to get bug reports about it. If you don't have time to dig into this, do you by any chance know anyone who does? REPOSITORY R241 KIO BRANCH master REVISION DETAIL https://phabricator.kde.org/D18798 To: anemeth, #frameworks, kde-frameworks-devel, ngraham, davidedmundson Cc: pino, elvisangelaccio, ngraham, kde-frameworks-devel, michaelh, bruns
