Agenda discussion for public meeting on 2025-12-04

[Rob--W]

This issue is used to collect topic suggestions for our December 4, 2025 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 915: Inconsistency: tabs.query behavior for permissions granted by content_scripts.matches
  • Issue 916: Sidepanel API: Behavioral inconsistencies with Chrome and Edge implementations
  • Issue 917: Proposal: Add management.readOnly permission for read-only access to management API
  • Issue 918: Grant time-based user activation from extension events that grant a user gesture
  • Issue 919: Should user gestures be curried between contexts?
  • Issue 920: Should extension APIs consume user activation?
• Timely issues (10 minutes)
  • PR 802: Add proposal for topFrameMatches and excludeTopFrameMatches
  • PR 885: Correct iconVariants and colorSchemes casing. Add NotificationOptions.iconVariants
  • (nominated issues here)
• Check-in on existing issues (20 minutes)
  • Issue 449: Provide way of handling unsupported DNR rule

[kzar]

@kiaraarose if it's not too late, could we add #449 (comment) to the agenda?

For context, we have prepared topDomains/excludedTopDomains matching for the declarativeNetRequest rules, and just need to get the feature detection question cleared up so folks can start using it. My proposal for that was to make declarativeNetRequest.RuleConditionKeys enumerable, so folks could quickly check which rule conditions are supported, like they can with other parts of the API like declarativeNetRequest.RuleActionType. I think it was previously discussed in one earlier meeting, but I unfortunately couldn't attend.

(cc @oliverdunk)