[Webapps] fix new webapp container matching in bamf

Bug #1289498 reported by Alexandre Abreu on 2014-03-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
BAMF
Critical
Alexandre Abreu
bamf (Ubuntu)
Undecided
Unassigned

Bug Description

The new webapp containers (not in the browsers anymore) use a mixture of specific executable dispatcher (unity-webapps-runner & webapps-container) and a specific StartupWMClass in the desktop file to allow bamf & unity to properly match & have a consistent behavior in the launcher.

At the moment, the matching is broken:
- 2 windows can appear for the same webapp,
- raising launches a new webapp,

Related branches

Changed in bamf:
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Alexandre Abreu (abreu-alexandre)
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:bamf at revision 595, scheduled for release in bamf, milestone Unknown

Changed in bamf:
status: In Progress → Fix Committed
Changed in bamf:
milestone: none → 0.6.0
Changed in bamf (Ubuntu):
status: New → In Progress
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bamf - 0.5.1+14.04.20140310-0ubuntu1

---------------
bamf (0.5.1+14.04.20140310-0ubuntu1) trusty; urgency=low

  [ Alexandre Abreu ]
  * Remove old webapp related code since now we dont use browser tab
    matching anymore. (LP: #1289498)
 -- Ubuntu daily release <email address hidden> Mon, 10 Mar 2014 22:29:08 +0000

Changed in bamf (Ubuntu):
status: In Progress → Fix Released
Changed in bamf:
milestone: 0.6.0 → 0.5.1

Fix Released in bamf BAMF 0.5.1 "The Trusty BAMF".

Changed in bamf:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers