Bug 344245 - Incontask dont separe correctly Google Chrome Apps
Summary: Incontask dont separe correctly Google Chrome Apps
Status: RESOLVED DUPLICATE of bug 315488
Alias: None
Product: plasmashell
Classification: Plasma
Component: Icons-only Task Manager (show other bugs)
Version: 5.2.0
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-16 16:38 UTC by Tete
Modified: 2015-02-24 01:03 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tete 2015-02-16 16:38:45 UTC
When you have various Google Chrome Apps, and you start to open it, all are grouped in Google Chrome's "Windows stack" this shouldn't be like that, every Application should have his own Icon

Reproducible: Always

Steps to Reproduce:
1. Open Chrome
2. Open a Google Chrome App
3. you can see that they are in the same "Window stack"

Actual Results:  
Here is few examples (it even looks a bit weird when first, you open an app like "Inbox" and then Chrome, the wole stack uses "Inbox icon")
1) Here first i opened Google chrome then Inbox http://i.imgur.com/EsEMexb.png
2) Here first i opened Inbox then Google Chrome http://i.imgur.com/Q8qlZsc.png

Expected Results:  
Check this Evolve OS capture you can see how that taskbar separe correctly all Google Chrome Apps https://plus.google.com/u/0/communities/103032596316713958671/stream/ffba5ab4-c468-4d5f-a9e9-ab2bd037b542

Qt: 5.4.0
KDE Frameworks: 5.7.0
Plasma 5.2.0
Comment 1 Tete 2015-02-16 16:42:30 UTC
if that link to EvolveOS screenshot dont open correctly, here is another http://i.imgur.com/StHV0hb.png
Comment 2 Tete 2015-02-22 22:46:32 UTC
now im just checking Gnome Shell, and the taskmanger, get the expected result too http://i.imgur.com/kb7W8g7.png
Comment 3 Tete 2015-02-23 23:45:13 UTC
BTW it's still not solved yet, sorry for duplicate!, thx guys!

*** This bug has been marked as a duplicate of bug 315488 ***