https://bugs.kde.org/show_bug.cgi?id=516184
--- Comment #10 from Nate Graham <[email protected]> --- (In reply to David Edmundson from comment #7) > If we genuinely believe this is critical should we revert the original patch? I know it sucks having the bug title in red on lists and such. But I'm just following our own guidelines here. > Hiding in the expose effect on both and local machine is also a slight > deviation from the text strictly says, but shouldn't blow up the code. > Android does this for banking apps so there's some sort of justification > there. We can also claim it solves some cases of accidental exposure +1, even if it looks weird, I think that's better than leaking potential PII. (In reply to Fernando Marcelino Muniz from comment #8) > Does the same argument apply for virtual keyboards interacting with hidden > windows? Assuming they also get hidden, it's still easy to know what is > being typed from the pointer's position. > The average user would assume that the virtual keyboard is being hidden due > to it being focused on the hidden window, and they'll likely not even > consider that the pointer position is giving away what they're typing. No; you're interpreting the feature to be a broader thing than it is, and to do things that it doesn't say or imply that it will do. Again, if your privacy needs are truly that high, don't screencast while you're doing the private thing. This is simple common sense. -- You are receiving this mail because: You are watching all bug changes.
