[Falkon] [Bug 400753] Add support for custom StartupWMClass

2018-12-26 Thread Alexandre Pereira
https://bugs.kde.org/show_bug.cgi?id=400753 --- Comment #5 from Alexandre Pereira --- thanks for you comment. It would be really cool. The way I am using falkon is to have a default profile where I do normal web browsing, and then have falkon with custom profiles ( where I pick a template

[Falkon] [Bug 400753] Add support for custom StartupWMClass

2018-12-25 Thread David Rosca
https://bugs.kde.org/show_bug.cgi?id=400753 --- Comment #4 from David Rosca --- (In reply to Alexandre Pereira from comment #3) > Will this work on wayland too ? No, on Wayland there is no WM_CLASS, instead the appId (at least width xdg-shell) is used to match windows with launchers. So for

[Falkon] [Bug 400753] Add support for custom StartupWMClass

2018-12-25 Thread Alexandre Pereira
https://bugs.kde.org/show_bug.cgi?id=400753 --- Comment #3 from Alexandre Pereira --- Thank you !! very much I will test ASAP on opensuse git packages ! Will this work on wayland too ? -- You are receiving this mail because: You are watching all bug changes.

[Falkon] [Bug 400753] Add support for custom StartupWMClass

2018-12-24 Thread David Rosca
https://bugs.kde.org/show_bug.cgi?id=400753 --- Comment #2 from David Rosca --- It doesn't work the way you described. StartupWMClass is not there to dictate the application to use this class, instead it is there for launchers to know what WM_CLASS will the started application have. You can now

[Falkon] [Bug 400753] Add support for custom StartupWMClass

2018-12-24 Thread David Rosca
https://bugs.kde.org/show_bug.cgi?id=400753 David Rosca changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|