https://bugs.kde.org/show_bug.cgi?id=520410
--- Comment #2 from Kristen McWilliam <[email protected]> --- Can confirm as well. It is _kind of_ a Chromium bug, in that when pressing the compose key it immediately sends a surrounding_text change event, which makes plasma-keyboard think the compose sequence has been aborted. They probably _shouldn't_ be doing that, but.. a bunch of apps seem to do so pretty arbitrarily. It might require us to re-think how we handle compose/dead keys state, given that we can't trust apps and toolkits to do the expected thing. -- You are receiving this mail because: You are watching all bug changes.
