New issue
Advanced search Search tips

Issue 593722 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Chrome 49 / chrome.runtime.onInstalled indefinitely fired when extension is updated manually in developer mode from chrome://extensions

Reported by emmanuel...@verifrom.com, Mar 10 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

Steps to reproduce the problem:
1. Install extension in dev mode (catching chrome.runtime.onInstalled event)
2. Update version in manifest
3. Go back to chrome://extensions
4. Update extension by clicking on the update button
5. The onInstalled event is indefinitely fired in the background script 
6. Close the chrome://extensions tab
7. Event is not thrown anymore

What is the expected behavior?
event should be fired only once

What went wrong?
The onInstalled event is fired while the chrome://extensions tab is opened. Closing the tab will stop this "phenomenon"

WebStore page: 

Did this work before? Yes Before Chrome 49 I never had any problem with my extensions

Chrome version: 49.0.2623.87  Channel: stable
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 21.0 r0

Comment 1 by emmanuel...@verifrom.com, Mar 10 2016 

I found what is the problem.

My handler of the onInstalled makes a reload of tabs matching specific URLs selected using chrome.tabs.query.
But... my extension lacks the "tabs" permission.
So... the reload is applied to all tabs opened, including chrome://extensions

Apparently, reloading (chrome.tabs.reload(tabId)) the chrome://extensions tab has now the same action as clicking on the update button.
I would swear it was not the behavior before Chrome 49, since the code and manifest was not changed since that version.

Comment 2 by emmanuel...@verifrom.com, Mar 10 2016 

Maybe the change is in chrome.tabs.query.

Whatever, the behavior is now - I suppose - as expected.
Thus, this is my issue, not yours.

Comment 3 by lima...@gmail.com, Mar 10 2016 

Yes, Because of security issue, We made a change on chrome.tabs.query.

To 'title' or 'url' with chrome.tabs.query, you need a 'tabs' permission.

Comment 4 by lima...@gmail.com, Mar 10 2016

Status: WontFix (was: Unconfirmed)
►

Sign in to add a comment