https://bugs.kde.org/show_bug.cgi?id=356343
--- Comment #11 from Hugo Pereira Da Costa <hugo.pere...@free.fr> --- (In reply to Thomas Lübking from comment #10) > How could anything in konsole match ::acceptWidget, why would that expose > content on the window system layer and htf should palette setting mess with > input??? > no clue > There needs to be some other bug deeper down, I don't use networkmanager - > could you reproduce the input breaking with anything else but plasma-nm? > nope > What I could assume is that ::adjustPalette makes a call to the winId > though, and then nasty things can happen (which might also explain the > window-from-below exposure) > not that I know. > > About palette updates: > changes only impact children until the first child with Qt::WA_SetPalette is > met in the tree (they don't inherit the parenting palette but start a new > hierarchy) Which is the issue: when the style calls setPalette on a given widget it starts a new hierarchy. If the application set a custom palette on a parent widget, it will propagate untill it hits one modified by the style and break there. Not good. We react on application palette change (using a trick, because the widgets for which we changed the palette manually do not get the corresponding change event anymore), but not on parent widgets palette change. Anyway. That's OT. -- You are receiving this mail because: You are watching all bug changes.
