Agenda discussion for public meeting on 2026-01-29

[Rob--W]

This issue is used to collect topic suggestions for our January 29, 2026 meeting. We will stop accepting suggestions ~48 hours before the meeting and the final agenda will be added to the meeting notes doc ~24 hours before the meeting.

The content below this line will be copy-pasted to the agenda section of the meeting.

Agenda

The meeting will start at 3 minutes after the hour.
See issue 531 for an explanation of this agenda format.

• Announcements (2 minutes)
• Triage (15 minutes)
  • Issue 939: Feature request: Support for WEBP as a possible extensionTypes.ImageFormat option
  • Issue 940: Provide a way to distinguish prefetch requests from regular navigations in extension APIs
  • Issue 941: Enhancement: management.ExtensionInfo.disabledReason - add value that indicates the extension has been diabled due to incompatibility or even just client-specific reason
  • Issue 944: Feature request: in-memory storage that persists across extension reload/update
  • Issue 945: DNR URL matching and percent encoding
• Timely issues (10 minutes)
  • (nominated issues here)
• Check-in on existing issues (20 minutes)
  • Pull 932: Update runtime.onLoadedReason to match runtime.OnInstalledReason
  • Issue 521: sidePanel API: sidePanel.close() and sidePanel.toggle()
  • Issue 422: Inconsistency: limits on browser.alarms.create()
  • Issue 463: Inconsistency in browser.action: windowId key and enable()/disable() arguments

[carlosjeurissen]

Check-in on existing issue:
Issue 521 sidePanel.toggle()

Find agreement and merge:
PR 932 Update runtime.onLoadedReason to match runtime.OnInstalledReason

[bershanskiy]

We might want to check in on #422, if Chrome 144 collected some data.

[Rob--W]

I'd like to discuss an existing issue: #463

* [Issue 463](https://github.com/w3c/webextensions/issues/463): Inconsistency in `browser.action`: `windowId` key and `enable()`/`disable()` arguments

[dotproto]

Closing this issue in preparation for the 2026-01-29 meeting.