From 757ee06c16d8f877b4e5711c755cf62e0e600b66 Mon Sep 17 00:00:00 2001
From: Carlos Jeurissen <1038267+carlosjeurissen@users.noreply.github.com>
Date: Fri, 14 Aug 2026 11:36:59 +0200
Subject: [PATCH] docs: add alarms.clearAll() return value Safari exception and
 future change

---
 .../add-ons/webextensions/api/alarms/clearall/index.md       | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/files/en-us/mozilla/add-ons/webextensions/api/alarms/clearall/index.md b/files/en-us/mozilla/add-ons/webextensions/api/alarms/clearall/index.md
index 7fbb35f940abb08..a77db448dd0ae71 100644
--- a/files/en-us/mozilla/add-ons/webextensions/api/alarms/clearall/index.md
+++ b/files/en-us/mozilla/add-ons/webextensions/api/alarms/clearall/index.md
@@ -22,7 +22,10 @@ None.
 
 ### Return value
 
-A [`Promise`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) that will be fulfilled with a boolean. This will be `true` if any alarms were cleared, `false` otherwise. Note that Chrome always passes `true` here.
+A [`Promise`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) fulfilled with a boolean. This is `true` if any alarms were cleared, `false` otherwise.
+
+> [!NOTE]
+> Chrome always passes `true` and Safari `undefined`. The return type is subject to change and may always return `undefined` for all browsers in the future. It is best to not rely on the return type.
 
 ## Examples