The fix for this bug has been awaiting testing feedback in the -proposed
repository for quantal for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-chromium-extension in Ubuntu.
https://bugs.launchpad.net/bugs/1068308

Title:
  Race condition related to integration/install infobar

Status in Chromium extension: Unity Integration:
  Fix Released
Status in “unity-chromium-extension” package in Ubuntu:
  Fix Released
Status in “unity-chromium-extension” source package in Quantal:
  Fix Committed

Bug description:
  When browsing to a website for which a WebApp exists, an infobar
  appears to inform the user of the situation and propose an
  installation of the associated WebApp.

  The issue appears when multiple tabs are involved and one selects
  another tab while the current one is loading webpage for which a
  WebApp is available (but not installed or authorized). The infobar
  appears in the environment of the proper tab, but the text is empty.

  [Test Case]
  - have more than one tab opened (with blank pages),
  - in one of the tabs, go to a website that is supported by webapps (e.g. 
Twitter),
  - immediately after (BEFORE the website loads), switch to the other tab 
(Ctrl+Tab),
  - wait a bit for the original website to complete loading,
  - when one comes back on the loaded tab, an infobar should have popup but 
with NO text on it,

  [Regression Risks]
  The code deals with the infobar that the user sees when a WebApp is about to 
be installed or needs authorization. A malfunction might prevent WebApps from 
being installed or no installation message could be displayed.

  
  Technical:
  --------------

  There is a race condition in the infobar javascript that incorrectly
  uses a chrome.extension.getSelected function to get its current tab is
  a ask the background page for its text (since the infobar cannot
  receive init() data and has to get it from somewhere). The tab request
  is asynchronous hence the timing sensitivity of the operation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-chromium-extension/+bug/1068308/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to