Marc-André Bombeck 422decc9d9 fix(notifications): say when the browser's push service refuses ...

Enabling Browser Push showed only "Activation failed" whenever
pushManager.subscribe() rejected. Brave keeps push messaging off by
default and rejects with "AbortError: Registration failed - push
service error", which left people with nothing to act on.

The browser's own refusal is now classified apart from the server
answers around it. An AbortError from subscribe reads as the push
service refusing and links the Browser Push docs; in Brave the message
names the setting under brave://settings/privacy. A blocked permission
stays blocked, and a dismissed prompt or a rejected key keeps the
generic message. The subscribe flow moves out of the card component so
it stays under the function size baseline.

Refs Discussion #1378

2026-11-14 08:56:25 +01:00

..

de.json

fix(notifications): say when the browser's push service refuses

2026-11-14 08:56:25 +01:00

en.json

fix(notifications): say when the browser's push service refuses

2026-11-14 08:56:25 +01:00

es.json

fix(notifications): say when the browser's push service refuses

2026-11-14 08:56:25 +01:00

fr.json

fix(notifications): say when the browser's push service refuses

2026-11-14 08:56:25 +01:00

it.json

fix(notifications): say when the browser's push service refuses

2026-11-14 08:56:25 +01:00

ko.json

fix(notifications): say when the browser's push service refuses

2026-11-14 08:56:25 +01:00

nl.json

fix(notifications): say when the browser's push service refuses

2026-11-14 08:56:25 +01:00

pl.json

fix(notifications): say when the browser's push service refuses

2026-11-14 08:56:25 +01:00

pt-BR.json

fix(notifications): say when the browser's push service refuses

2026-11-14 08:56:25 +01:00

ru.json

fix(notifications): say when the browser's push service refuses

2026-11-14 08:56:25 +01:00