Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agenda discussion for public meeting on 2025-02-13 #754

Closed
Rob--W opened this issue Jan 30, 2025 · 7 comments
Closed

Agenda discussion for public meeting on 2025-02-13 #754

Rob--W opened this issue Jan 30, 2025 · 7 comments
Assignees
Labels
agenda Discuss in future meetings

Comments

@Rob--W
Copy link
Member

Rob--W commented Jan 30, 2025

This issue is used to collect topic suggestions for our February 13, 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 755: Proposal: about: matching
    • Issue 756: Proposal: Exclude Matching
    • Issue 762: DNR: Add excludedTopFrameDomains (and topFrameDomains)
    • Issue 763: Proposal: Add excludeTopFrameMatches and excludeTopFrameGlobs
  • Timely issues (10 minutes)
    • Issue 760: Specification for loading extensions in WebDriver Classic
  • Check-in on existing issues (20 minutes)
@Rob--W Rob--W added the agenda Discuss in future meetings label Jan 30, 2025
@erosman
Copy link

erosman commented Jan 31, 2025

Please note new topics #755, #756 and update to the previously discussed #746

@oliverdunk
Copy link
Member

Suggesting #762 for the new issues section.

@twschiller
Copy link

Proposing discussion/clarification of panel lifecycle when a different browser/extension panel is opened (are browsers supposed to close the existing panel, or does it just become inactive): #517 (comment)

@polywock
Copy link

Please include #763.

@kiaraarose
Copy link
Contributor

suggesting #760 for the timely issues

@dotproto
Copy link
Member

Closing in prep for tomorrow's meeting. Thanks for the suggestion, everyone! :D

@chrmod
Copy link

chrmod commented Feb 13, 2025

Any chance to include #764? Maybe as a part of #760

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agenda Discuss in future meetings
Projects
None yet
Development

No branches or pull requests

8 participants