New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 707732 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

From command palette: I can disable JS, but can't re-enable

Reported by remysh...@gmail.com, Apr 3 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3061.0 Safari/537.36

Steps to reproduce the problem:
1. open command palette, select "Disable JavaScript", enter.
2. re-open palette, search "javascript", only "disable javascript" shows
3. Refreshing makes no difference.

What is the expected behavior?
Once javascript is disabled, I should be able to re-enable via the command palette.

What went wrong?
There's no option to re-enable.

Did this work before? Yes Previous version of Canary (I *think*).

Chrome version: 59.0.3061.0  Channel: canary
OS Version: OS X 10.10.3
Flash Version: 

The command palette, I think, has changed. I see a `>` character, which if I remove I can search for files. So I think it's now been merged with file search, so that's where…I suspect… the issue is around.
 

Comment 1 by ajha@chromium.org, Apr 4 2017

Labels: Needs-Triage-M59 Needs-Bisect
Cc: sureshkumari@chromium.org
Labels: Needs-Feedback
Tested the issue on Mac-10.12.3, Windows-7 and Linux Ubuntu-14.04 using chrome version 59.0.3062.0 and 59.0.3061.0 with below steps
1.Opened dev tools in chrome
2.Clicked on "Disable JavaScript" in Settings and pressed enter
3.Restart the Chrome 
Observed that the "DisableJavaScript" is unchecked.
Please find the attached screencast and let us know if anything missed from our side to reproduce the issue.

Thanks.

707732.mov
7.4 MB Download
Owner: einbinder@chromium.org
Status: Fixed (was: Unconfirmed)
This was fixed in Canary here: https://codereview.chromium.org/2793873002/

Although #2 did not properly show how the bug occurred we caught what you meant.

Thanks!

Sign in to add a comment