-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notifications not even trying to appear #50
Comments
Could chromium/chromium@bb92cbc and possibly chromium/chromium@7a7a41c be the reason? |
I suppose so... welp... how do we bring them back then? just revert these? |
@crudebuster Both of these were reverted in the M122 version. Are you using that version and the problem still persists? Does this problem happen in Supermium M122? |
I've only tried the beta but I'll check it again. |
@crudebuster @llExSt I think I know why it is. I recently enabled a change to make notifications less intrusive, but some people want them. Go to |
Done that, the setting was already in, the notification engine seems completely disabled. |
@crudebuster Oof. In that case, this is probably something win32ss will have to fix. |
In Supermium 124 the notifications work again in Win7 so i'll wait for your update to Thorium. |
Do you have plans to update Thorium to match Supermium's version? The notification issues is still not fixed. |
System Details
Problem
Site Notifications are gone. No sign of them whatsoever. Nothing for download, instant messages, emails, only sounds by an extension I use to warn after a successful download.
Additional Notes
After I upgraded from M109 to M119 I knew I had to refresh passwords and such but after I did it no notification toasts appear whatsoever... I noticed too late and now the password manager won't save anything since I backtracked and went back to use M109.
I hope it's something dumb I did but I'm afraid the thing simply doesn't work because of some dumbassity I did and now I need to redo the god damn profile and account, I guess.
P.S.: Problem persists in 122, tested again in 122.0.6261.168, no go.
The text was updated successfully, but these errors were encountered: