https://bugs.kde.org/show_bug.cgi?id=315488
--- Comment #27 from GaryM <garymarty...@gmail.com> --- Forgot to say. When using the launcher rules you can have multiple launchers which work as desired but then vanish when grouping kicks in only to then reappear when their linked application is closed. I understand what you were saying about Google changing the ClassName for webapps, but it seems the current situation is that it works for launchers, but not grouping, resulting in some quite interesting behaviours when the launchers also stack into the group and then pop back out again. If the ClassName is never used in grouping, I'm unclear what benefit there is to linking a launcher to a specific ClassClass and ClassName. It would seem to only make sense to link a launcher to a specific ClassClass otherwise you get this slightly unexpected launcher stacking/hiding behaviour. -- You are receiving this mail because: You are watching all bug changes.
