Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

@caugner does the flagging as internal have any impact here, e.g., did they become public later than 21?

@caugner does the flagging as internal have any impact here, e.g., did they become public later than 21?

Good question!

I looked into it, and found that the events namespace has always been marked as internal since Chrome 21.

• From Chrome 21 to Chrome 27, it was in chrome/common/extensions/api/events.json.
• In Chrome 28, it was moved in chromium/chromium@52eafbd.
• From Chrome 28 to Chrome 39, it was in chrome/common/extensions/api/_api_features.json.
• In Chrome 40, it was moved in chromium/chromium@c93416a.
• Since Chrome 40, it is in extensions/common/api/_api_features.json.
• Today, it still marked as internal in that file: https://github.com/chromium/chromium/blob/main@{2025-04-27}/extensions/common/api/_api_features.json#L177-L178

Looking at https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/events, it doesn't surprise me that these types are marked as internal. If I understand these types correctly, they aren't used directly.

Although the commit message in Chrome 40 may suggest that events was only made available in that version, I rather think that those types were available since Chrome 21.

@rebloor Does that make sense?

PS: https://developer.chrome.com/docs/extensions/reference/api/events doesn't mention any Chrome version.