Can you confirm if there is even a current workaround for this?  I did manage to paste the chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo and very surprisingly it did resolve it and change it to the friendly app name in this case of "Tampermonkey" with the extension logo in the defined sites settings (I had never tried forcing an extension ID there) but no matter what I do to try to manually set the notifications permission to allow there, it does not seem to have any impact in this case and again allow the blocked extension to again send the desktop notifications through.

So, depending on how much is perhaps just not wired to handle extensions in sites settings GUI, at least SOME of it does appear to be wired as of now to at least give the impression that perhaps the possibility of using the same "sites" method to handle extension notifications may actually be a viable option.

Is it just me or is this not a pretty visible UI bug when it is just impossible to re-enable and turn notifications back on for ANY/ALL chrome extensions?

It may sound trivial to state that full removal of an extension and wipe of it's settings to then re-install is an acceptable method to re-enable their notifications, but in the case of extensions with large amount of stored data (without even also thinking about Chrome sync issues) this is simply not a realistic ask so hopefully this can at least be acknowledged as a reproducible bug and addressed sooner rather than later.

TIA for hopefully getting this triaged soon!

Adding proper component for someone from the respective team to have a look into this. Phani@ to help with triage.

Able to reproduce the issue on reported latest dev 68.0.3423.2,Beta 67.0.3396.40  & on latest chrome 68.0.3429.0 using Windows 7 &10,Mac OS 10.13, Ubuntu 14.04. Hence providing bisect information below

Bisect Info:
================
Good build: 63.0.3220.0
Bad build: 63.0.3221.0

You are probably looking for a change made after 503076 (known good), but no later than 503089 (first known bad).

CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/f9b4c77f094c17f529233ff29fc89bccdac48a3e..0601e5375167f5894c2ffa22b81e7a6528637579

suspect: https://chromium.googlesource.com/chromium/src/+/0601e5375167f5894c2ffa22b81e7a6528637579

Reviewed-on: https://chromium-review.googlesource.com/662997

@patricialor: Please confirm the issue and help in re-assigning if it is not related to your change.

Thanks!

Yeah, this is not great.

Justin, do you recall whether extension settings continued to show up in chrome://settings/content/notifications when we removed the notification center from the desktop platforms? I *think* they did, but I can't find the discussions anymore.

Hwi, would you have an opinion on where to surface such a toggle? Content Settings never was an ideal place even if we included it there, and since there's now a "Details" page for items on chrome://extensions/ we could add a toggle there when the extension has the "notifications" permission. I've attached a rough mock of something that could work?

In either case, this doesn't have to block the stable release.

Deleted: extension-details.png 59.7 KB

	extension-details.png 59.7 KB View Download

c6:

+jawag (Extensions), +namratakannan (WebUI) - does c6 sound good to you? 

Adding the notification toggle below Permissions section SGTM (as shown on the mock on c6)

Peter, I can't remember exactly. I think all we showed were notifications exceptions for domains with hosted extensions that were granted notifications permission.

While the chrome://extensions page is convenient, it is not something we ever expect users to navigate to.  So if this is put there I'd hope there is a plan to also add a section to chrome://settings somewhere.

Guys this is awesome and I love that mockup showing it added to the extensions page.  I disagree very much with @dewittj I really think more folks than he thinks will find it there if they ever need it.  Reason is simple - only those who either have enough knowledge to know what they did and want to re-enable an extension's notifications, or the only others that would need it - those totally in the dark and going after that setting directly as instructed by some person or doc, anyway! :)

Any ETA on when we'll finally see this change live?  TIA!

Just checking if there is any update on the changes you proposed above.

I've spent 45 minutes looking for a way to reverse this... Neither the Content Settings or the Extension Settings pages seem to have any way to reverse this...

I accidentally disabled notifications for a plugin I absolutely need, and now there's no way to get it back... Can someone please update on the status of this issue?

***Mass UI Triage***

Adding labels for expert review.