New issue
Advanced search Search tips

Issue 817638 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Feature



Sign in to add a comment

Do not remove the checkbox to disable crashed extensions

Reported by jidanni@gmail.com, Mar 1 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.74 Safari/537.36

Steps to reproduce the problem:
On chrome://extensions/ if an extension crashes, it's "[ ] Enabled"
checkbox disappears, and is replaced with a "Reload" link.

This forces one to reload it if one wants to disable it.

Please leave the checkbox there.

No I don't want to remove the extension.

What is the expected behavior?

What went wrong?
There is even a race condition created: the user must click the checkbox before it crashes again.

WebStore page: 

Did this work before? No 

Chrome version: 65.0.3325.74  Channel: n/a
OS Version: 
Flash Version:
 
Labels: Needs-Triage-M65
Labels: -Type-Bug Triaged-ET M-66 FoundIn-66 OS-Mac OS-Windows Type-Feature
Status: Untriaged (was: Unconfirmed)
As per comment #0, this seems to be a feature request. Hence, marking it as untriaged for further inputs from dev team.

Thanks...!!
Components: -Platform>Extensions UI>Browser>ExtensionsManagement
[Extensions Triage] Looks to be an issue with the MD Extensions Page.

Comment 4 by jawag@chromium.org, Mar 21 2018

Labels: Needs-Feedback
Thanks for the suggestion. Can you provide more info on your use case for this?

Comment 5 by jidanni@gmail.com, Mar 22 2018

Don't you think it is bad if

This forces one to reload it if one wants to disable it.

And then it just crashes again,

This forces one to reload it if one wants to disable it.

And then it just crashes again,

you see what I mean?

Comment 6 by jidanni@gmail.com, Mar 22 2018

To reproduce, make an app that crashes.
Owner: jawag@chromium.org
Status: Assigned (was: Untriaged)
Mac triage: assigning to jawag@ from #4.

Sign in to add a comment