Skip to content

Commit b841475

Browse files
authored
[WebExtensions] Chrome 150 plans to limit alarm name lengths (mdn#43933)
Chrome 148 introduced a console warning for alarm names longer than 1024 bytes.[1] Safari devs believe "1024 is a good limit".[2] Firefox will likely "take a wait and see approach".[3] Sources: [1] chromium/chromium@432c30e [2] w3c/webextensions#935 (comment) [3] https://github.com/w3c/webextensions/blob/main/_minutes/2026-03-12-wecg.md
1 parent a21bf85 commit b841475

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

  • files/en-us/mozilla/add-ons/webextensions/api/alarms/create

files/en-us/mozilla/add-ons/webextensions/api/alarms/create/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,8 @@ browser.alarms.create(
2929

3030
Alarm names are unique within the scope of a single extension. If an alarm with an identical name exists, the existing alarm will be cleared and the alarm being created will replace it.
3131

32+
From Chrome 150, alarms with names longer than 1024 bytes are rejected. This limit may be implemented on other browsers. See [Proposal: Limits on lengths of strings passed to WebExtension APIs](https://github.com/w3c/webextensions/issues/935) for more information.
33+
3234
- `alarmInfo` {{optional_inline}}
3335
- : `object`. You can use this to specify when the alarm will initially fire, either as an absolute value (`when`), or as a delay from the time the alarm is set (`delayInMinutes`). To make the alarm recur, specify `periodInMinutes`.
3436

0 commit comments

Comments
 (0)