2

So people are doing more and more stuff directly in browsers like Chrome and Firefox, as opposed to in separate desktop applications.

The windowing paradigm of the desktop was created in an age in which every application had its own window. However, in an age where we have a mix of desktop applications and applications that we run inside browsers, and our browsers host 10s or even 100s of tabs, as a user I need to take two steps instead of one to access a particular browser application running in a tab. I need to a) switch to the relevant window of my browser, and then b) switch to the relevant tab within that window hosting the application I want.

Ok, so what do I do? I drag application tabs out into their own Windows -- now I only need to find that specific Window in my tab switcher / task bar / present windows view. HOWEVER, from Kwin's perspective that WIndow is just Google Chrome/Firefox/whatever. Its not my "Gmail" or whatever app that window now represents. It gets grouped along with my other Chrome windows rather than being kept separate. In present windows, I can't type "Gmail" and have it come up.

Short of having browsers support this directly (which at least the Chrome folks are working on with PWAs [1], but I believe that requires support from the web site author as well), I'd love some special support from KWin to handle this "new world order". I'd like to classify a specific browser window with a different application name, ideally a separate icon, and have KWin treat it for all intents and purposes as a separate application.

Perhaps a general solution which would work for this use case and others is a "labeling" approach. If Kwin allows me to attach arbitrary labels to Windows, and then allows me to search by label in present windows, and to group by label in the task manager / present windows, then it would be enough to solve this problem, while being completely backward compatible for people who do not use the new labels feature, as well as being completely generic.

[1] https://developers.google.com/web/updates/2018/05/dpwa and https://developers.google.com/web/progressive-web-apps/