Giters

w3c / webextensions

Charter and administrivia for the WebExtensions Community Group (WECG)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Agenda discussion for public meeting on 2024-03-14

Rob--W opened this issue · comments

commented

This issue is used to collect topic suggestions for our March 14, 2024 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)
    • Simeon's affiliation
    • Meet up in San Diego 18-20
  • Triage (15 minutes)
    • Issue 557: Proposal: Extension Loading Priority
      • Creator: @erosman
      • Goal: Discuss whether this is an issue we should address and, if so, identify next steps.
    • Issue 558: Proposal: allow for programmatic access to extension publisher information
      • Creator: @msfrisbie
      • Summary: In order to allow "extension manager" extensions to react to ownership changes, browser.management should expose information about an extension's developer.
      • Goal: Discuss whether it makes sense to expose developer metadata to other extensions.
    • Issue 563: ExecutionWorld and StyleOrigin should use lowercase values
      • Creator: @xeenon
      • Summary: Issue suggests aligning on how we handle the casing of constant and enum string values.
      • Goal: Determine next steps for this issue.
    • Issue 565: Support multiple user script worlds in the user scripts API
      • Creator: @rdcronin
      • Goal: Identify how this issue is different from PR 560. NOTE: 560 is the next topic.
  • Timely issues (10 minutes)
    • PR 560: Proposal: Multiple user script worlds
      • Creator: @rdcronin
      • Summary: New proposal expanding the userScripts API to support per-script worlds.
    • PR 529: Add permissions.requestSiteAccess() API proposal
      • Creator: @EmiliaPaz
      • Summary: Emilia has updated the proposal based on feedback since last meeting.
  • Check-in on existing issues (20 minutes)
    • Issue 547: Proposal: document browser.storage.managed initialization semantics and provide initialization event
    • Issue 538: Proposal: RegisteredContentScript.workers property to inject WorkerScope(s)
commented

The following two issues were part of the previous agenda but were not covered:

  • Issue 547: Proposal: document browser.storage.managed initialization semantics and provide initialization event
  • Issue 538: Proposal: RegisteredContentScript.workers property to inject WorkerScope(s)

There were many more non-covered issues, and during the last meeting @xeenon expressed the thought that we should perhaps have a label to distinguish issues that have been handled versus those that have not been.

commented

Requesting discussion on #521.

This topic was slated for discussion under #535, but I can't find any notes on it. Was it perhaps due to a strict time constraint?

Thank you, @Rob--W!

commented

Requesting discussion about Side Panel ability to set min/max width programmatically in order to improve user experience on using Side Panel.

I couldn't find related issue on GitHub, but this was asked several times here: https://groups.google.com/a/chromium.org/g/chromium-extensions/c/cJmdMLmpbjg/m/TUsOt2U8AQAJ

Thank you team, much appreciated.

commented

Because there were more topics than we had time to cover, and the fact that Chrome is the only implementation of the sidePanel API, we decided to prioritize other topics over sidePanel a few meetings ago. The Chrome folks should chime in on the thread.

commented

Closing in prep for the meeting in ~8 hours.