Chrome Version: 69.0.3497.92 (Official Build) Revision	eb2c6d16bcb960cc5c322243c1771713460c4bcf-refs/branch-heads/3497@{#921}(32/64-bit)
OS: Windows (7,8,8.1,10), Mac(10.12.6, 10.13.1, 10.13.6, 10.14)

Pre-condition: 
1. Sign in to chrome with a valid credentials
2. The chrome account used for sign in should have atleast one synced post side extension in disabled state(for eg: Grammarly for Chrome)

What steps will reproduce the problem?
1. Launch Chrome, observe that the added extension is side loaded in disabled state.(i.e. warning is shown in the Wrench Icon 'Grammarly for Chrome is disabled' .
2. Now navigate to chrome://extensions and try enabling the extension(in this case Grammarly for Chrome) by clicking on the corresponding toggle button.
3. Observe that a dialog box is shown with 'Re-enable' and 'Cancel' button.
4. Now click on 'Cancel' button or the 'x' (close button) of dialog box and observe the state of the toggle button in the extension card.

Actual  :Toggle button state appears enabled even when extension is still in disabled state.
Expected:Toggle button should change back to disabled state after user clicks on 'Cancel' button of dialog box.

This is a non-regression issue, seen from M-65 series(since new UI for chrome://extensions is introduced from this series)

Kindly review the attached screen-cast for reference.

Note: Issue is not seen on Linux (14.04LTS)

Thank you!

 

Deleted: ActualVideo.mp4 817 KB

	ActualVideo.mp4 817 KB View Download