Regression: cmd-R no longer reloads unpacked extensions
Reported by
bgros...@gmail.com,
May 9 2018
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. load an unpacked extension 2. make a change to the extension's manifest.json file (e.g. to its description) 3. navigate to chrome://extensions and hit cmd-R (mac) to reload. 4. check the extension's description to verify the change` What is the expected behavior? Cmd-R should reload the extension. What went wrong? The extension is not reloaded. Did this work before? Yes Chrome version: 65.0.3325.181 Channel: n/a OS Version: OS X 10.12.6 Flash Version: Shockwave Flash 29.0 r0 Clicking the reload button still reloads the extension, but cmd-R no longer does.
,
May 10 2018
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 17.10 using chrome stable version #66.0.3359.139 and latest canary #68.0.3425.0. Issue is not reproducible in chrome reported version #65.0.3325.181 This is a non-regression issue as it is observed from M66 - 66.0.3343.0 from the introduction of MD-extensions at chrome://extensions. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
May 11 2018
,
Aug 18
Bumping this hoping there might be some new info? This regression introduces a significant slowdown in the Extension development process/workflow. This pattern happens over and over: 1. Make a change in the code, 2. Go back to Chrome, 3. Navigate to the extensions page (if needed) 4. Reload the extension 5. Move to relevant tab 6. Reload the page 7. Test the change When I'm working on an extension, I do this tens if not 100s of times in a day. Before the regression, this could all be done with keyboard shortcuts; now, developers have to use the mouse for step 4 and it adds several more mousing steps, such as scrolling to find the right extension, locating the reload button, and clicking the reload button. All of this was handled with a simple CMD-R previously. An alternative to reviving the previous behavior would be to allow a CMD-R reload on an unpacked extension's detail page to reload that extension. Currently, a reload of the details page does not reload the extension. Further, that page doesn't even have a mouseable reload button. Thanks!! |
|||
►
Sign in to add a comment |
|||
Comment 1 by susan.boorgula@chromium.org
, May 9 2018