1874960 - Broken UTF-16 string causes permanent fallback to XUL notification until restart

Status: RESOLVED FIXED

(Toolkit :: Alerts Service, defect)

Description

[Kagami Rosylight [:saschanaz] (they/them) (inactive until 2025-11-14)]

Running new Notification('7٩۰\r2󠏰‪󠘽󠞭9I%=◺o𯏡󠇈🩰‪칤󠥎󠆉ⁿ󠂏쬩𝆀𯞨#٩[\b7᩿󠣁鸲𝅧𨝊٫۹\r\n') triggers XUL notification for every other notification after that. But broken notification should not affect others.

Comment 1

[Kagami Rosylight [:saschanaz] (they/them) (inactive until 2025-11-14)]

This is tricky as falling back to XUL backend means notification.close() should be handled by the same backend. I think in this case it should just error out rather than falling back. Filed a spec issue because the relevant error behavior is currently not defined.

Comment 2

[Kagami Rosylight [:saschanaz] (they/them) (inactive until 2025-11-14)]

Attachment: Bug 1874960 - Stop falling back to XUL on Windows/macOS r=nalexander

The fallback is mainly for Linux where the lack of libnotify can cause error, in which case repeating to try native backend makes no sense. That does not apply to Windows and macOS.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/c159ee569750
Stop falling back to XUL on Windows/macOS r=nalexander

Comment 4

[Natalia Csoregi [:nataliaCs]]

https://hg.mozilla.org/mozilla-central/rev/c159ee569750