Reload of chrome://extensions/ causes unpacked (local) extension to reload
Reported by
andrey.k...@gmail.com,
Sep 20 2017
|
||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.91 Safari/537.36 Steps to reproduce the problem: 1. Load any unpacked extension with any console.log on startup (to catch extension restart) 2. Open chrome://extensions/ page 3. Reload chrome://extensions/ page What is the expected behavior? Unpacked extension should not be reloaded What went wrong? Unpacked extension is reloaded You can see demo here: https://youtu.be/xncclVUHaOo Did this work before? Yes Previous Chrome version Chrome version: 61.0.3163.91 Channel: stable OS Version: 10.0 Flash Version: 1. If DevTools console is open, this bug doesn't happen 2. Not sure it's related, but after latest Chrome update and following Chrome restart all pages having in URL chrome://extensions/ were replaced with chrome://chrome/extensions/ (this page doesn't exist) But it happened only once after the first restart after the update. After following restarts URL's are not replaced.
,
Sep 22 2017
,
Sep 25 2017
Unable to reproduce the issue on reported version 61.0.3163.91 , Latest Stable 61.0.3163.100 and Latest Canary 63.0.3223.1 using Windows 10, Ubuntu 14.04 with the below mentioned steps. 1.Loaded an unpackaged extension with console.log in the startup page 2.Opened chrome://extensions/ page 3.Reloaded chrome://extensions/ page @Reporter: could you please attach a sample unpackaged extension by which you are facing the issue, so that we can check with that particular file. Thanks.
,
Sep 25 2017
,
Sep 25 2017
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 26 2017
,
Sep 26 2017
Hi @vamshi In your video attached, I can't see you actually looking at the console output. The console.log message is intended to catch the extension being restarted. Bearing that in mind, steps to reproduce will be the following: 1. Open chrome://extensions, turn on "Developer mode" 2. Load the extension attached. 3. Open the extension's background page, console tab (you should see "Extension started" message) 4. Turn on timestamps (settings -> Show timestamps). Memorize the timestamp of "Extension started" message. 5. Reload chrome://extensions page. 6. You will see in the extension's background console a [new] message with a different timestamp - that means that extension was reloaded. Best regards, Andrey.
,
Sep 26 2017
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 26 2017
Able to reproduce the issue on mac os 10.12.6 , ubuntu 14.04 and windows 7 using chrome M61 #61.0.3163.100 and chrome M63 #63.0.3222.8 with steps mentioned in comment #8. This issue is seen from M50 and is a Non-regression issue. Marking it as untriaged for further inputs on this. Thanks!
,
Sep 29 2017
[Extensions triage] This is by design, see https://bugs.chromium.org/p/chromium/issues/detail?id=104662. Marking it as WontFix. Please re-open if necessary, explaining why you think this is a problem. |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by woxxom@gmail.com
, Sep 20 2017