[MD Extensions] "Errors" button only shows up after refreshing the page |
||||||
Issue descriptionRepro steps (see screencast too): 1) Open chrome://extensions in non-dev mode. 2) Turn on dev-mode from the toolbar. Expected "Errors" buttons for any extension that has errors should immediately show up. Actual "Errors" buttons do not show up, until page is refreshed. Similar behavior is observed for the reverse direction (turning off dev mode should hide "errors" buttons).
,
Dec 20 2017
Just to clarify, I am reproducing this with --disable-error-console flag. Did not try without it.
,
Dec 20 2017
Also attaching the previous UI's behavior for reference.
,
Feb 26 2018
,
Feb 27 2018
,
Feb 27 2018
,
Mar 6 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b1ea193294955a0b91a2d3b2b70f36ad2d29e059 commit b1ea193294955a0b91a2d3b2b70f36ad2d29e059 Author: Esmael El-Moslimany <aee@chromium.org> Date: Tue Mar 06 21:56:12 2018 MD Extensions: update extensions when dev mode toggled Bug: 796650 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I1dc50ba6eb8e7b2f01992fdcee5ade2d7c6f35e1 Reviewed-on: https://chromium-review.googlesource.com/940432 Commit-Queue: Esmael El-Moslimany <aee@chromium.org> Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by: Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#541210} [modify] https://crrev.com/b1ea193294955a0b91a2d3b2b70f36ad2d29e059/chrome/browser/extensions/api/developer_private/developer_private_api.cc
,
Mar 6 2018
,
Mar 7 2018
Able to reproduce the issue on chrome build without fix Verified the fix on Mac 10.12.6, Windows-10, Ubuntu 14.04 on Chrome version #67.0.3364.0 as per the comment#0 Attaching screen cast for reference. Observed "Errors buttons immediately for any extension that has errors" Hence, the fix is working as expected. Adding the verified label. Thanks! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dpa...@chromium.org
, Dec 20 2017