|
| 1 | +# WECG Meetings 2025, Public Notes, Aug 14 |
| 2 | + |
| 3 | + * Chair: Kiara Rose |
| 4 | + * Scribes: Rob Wu |
| 5 | + |
| 6 | +Time: 8 AM PDT = https://everytimezone.com/?t=689e7880,384 |
| 7 | +Call-in details: [WebExtensions CG, 14th August 2025](https://www.w3.org/events/meetings/43e4fb8e-4736-445c-b051-2383ffeef033/20250814T080000/) |
| 8 | +Zoom issues? Ping @zombie (Tomislav Jovanovic) in [chat](https://github.com/w3c/webextensions/blob/main/CONTRIBUTING.md#joining-chat) |
| 9 | + |
| 10 | + |
| 11 | +## Agenda: [discussion in #858](https://github.com/w3c/webextensions/issues/858), [github issues](https://github.com/w3c/webextensions/issues) |
| 12 | + |
| 13 | +The meeting will start at 3 minutes after the hour. |
| 14 | + |
| 15 | +See [issue 531](https://github.com/w3c/webextensions/issues/531) for an explanation of this agenda format. |
| 16 | + |
| 17 | + * **Announcements** (2 minutes) |
| 18 | + * [Issue 843](https://github.com/w3c/webextensions/issues/843): TPAC registration is open, we have ~12 hours of [meeting time scheduled](https://github.com/w3c/webextensions/issues/843#issuecomment-3140015582) across Monday and Thursday. |
| 19 | + * WG status |
| 20 | + * **Triage** (15 minutes) |
| 21 | + * [Issue 861](https://github.com/w3c/webextensions/issues/861): Enhancement request - Expand the Tab Groups API to include some info about Closed Tab Groups |
| 22 | + * [Issue 862](https://github.com/w3c/webextensions/issues/862): Proposal: Add sound to contentSettings |
| 23 | + * **Timely issues** (0 minutes) |
| 24 | + * N/A |
| 25 | + * **Check-in on existing issues** (20 minutes) |
| 26 | + * **Open discussion** |
| 27 | + * wpt/spec questions |
| 28 | + |
| 29 | + |
| 30 | +## Attendees (sign yourself in) |
| 31 | + |
| 32 | + 1. Rob Wu (Mozilla) |
| 33 | + 2. David Johnson (Apple) |
| 34 | + 3. Kiara Rose (Apple) |
| 35 | + 4. Simeon Vincent (Mozilla) |
| 36 | + 5. Timothy Hatcher (Apple) |
| 37 | + 6. Nathan Gross (random observer) |
| 38 | + 7. Jordan Spivack (Capital One) |
| 39 | + 8. Casey Garland (Capital One) |
| 40 | + 9. Mukul Purohit (Microsoft) |
| 41 | + |
| 42 | + |
| 43 | +## Meeting notes |
| 44 | + |
| 45 | +[Issue 843](https://github.com/w3c/webextensions/issues/843): TPAC registration is open, we have ~12 hours of [meeting time scheduled](https://github.com/w3c/webextensions/issues/843#issuecomment-3140015582) across Monday and Thursday. |
| 46 | + |
| 47 | + * [kiara] TPAC registration is open. Don't forget to sign up. We're meeting Tuesday and Thursday. |
| 48 | + |
| 49 | +WG status |
| 50 | + |
| 51 | + * [simeon] plh from W3C has taken our WG charter and submitted it for review in the W3C. |
| 52 | + * https://github.com/w3c/strategy/issues/146 |
| 53 | + * https://lists.w3.org/Archives/Member/w3c-ac-members/2025JulSep/0028.html |
| 54 | + * https://w3c.github.io/charter-drafts/2025/webextensions-wg.html |
| 55 | + * https://github.com/w3c/charter-drafts/blob/6db53d96914f6328a0fae3a917477933f0ca2a70/2025/webextensions-wg.html |
| 56 | + |
| 57 | +[Issue 861](https://github.com/w3c/webextensions/issues/861): Enhancement request - Expand the Tab Groups API to include some info about Closed Tab Groups |
| 58 | + |
| 59 | + * [kiara] Safari does not have tabGroups API yet. |
| 60 | + * [simeon] I believe that this issue was filed in response to a query in Mozilla Discourse from a developer |
| 61 | + * [rob] Feels like this might fit in the sessions API, which is about closed tabs and windows. |
| 62 | + * [simeon] Chrome and Firefox has concepts related to tab groups that do not require an existing tab. |
| 63 | + * [rob] Makes sense to add this to the tabGroups API. |
| 64 | + * [kiara] We will need to revisit this when Googlers are present in this meeting. |
| 65 | + |
| 66 | +[Issue 862](https://github.com/w3c/webextensions/issues/862): Proposal: Add sound to contentSettings |
| 67 | + |
| 68 | + * [kiara] We do not support the contentSettings API in Safari. Request seems reasonable. |
| 69 | + * [rob] We do not support the contentSettings API either. |
| 70 | + |
| 71 | +wpt/spec questions |
| 72 | + |
| 73 | + * [simeon] How do browsers approach bringing in WPT for general web platform features? |
| 74 | + * [timothy] We periodically pull and merge specific sections. |
| 75 | + * [rob] We do something similar. We regularly upstream/downstream tests from WPT as appropriate. |
| 76 | + * [timothy] Should we wait for 2 implementations before writing a test? |
| 77 | + * [rob] If there's interest from another browser, it makes sense to have it be a wpt test. If there is an API that is explicitly rejected by the other browsers, then it makes less sense. |
| 78 | + * [timothy] Example with offscreen documents API. Not implemented by Safari nor Firefox. |
| 79 | + * [kiara] Would we specify it? |
| 80 | + * [rob] Problem with that API is currently it's only a Chrome feature that is explicitly described as an aid to bridge migration from MV2 to MV3, with reasons that can be added/removed by Google at any time. It's not a stable feature. |
| 81 | + * [timothy] Was also designed before we had a process in the WECG. |
| 82 | + * [rob] So far we did not (and still do not) have very rigid/strict requirements here; as long as there is some alignment. |
| 83 | + * [timothy] Sounds like that outlines a litmus test. |
| 84 | + * [david] Do we all agree that WPT is essentially standards track and other capabilities are out of scope? |
| 85 | + * [simeon] Sounds good to me. |
| 86 | + * [rob] Sounds like a good take for the start of the discussion (explicitly not a final decision). |
| 87 | + * [timothy] Sounds good to me. |
| 88 | + |
| 89 | +[simeon] Spec progress |
| 90 | + |
| 91 | + * [kiara] Planning to start work on my contributions next week. |
| 92 | + * [simeon] Rob, do you know where Tom is on host permissions? |
| 93 | + * [rob] I don't know but I will ask him after the meeting. |
| 94 | + * [simeon] would it be helpful to create tracking issues for breaking down the spec work required? |
| 95 | + * [kiara] Open to the idea. I'm working on externally connectable, feel free to create an issue & assign it to me. |
| 96 | + * [rob] Also not opposed. Could be useful especially when we need to come back to something after a few weeks. |
| 97 | + |
| 98 | +The next meeting will be on [Thursday, August 28th, 8 AM PDT (3 PM UTC)](https://everytimezone.com/?t=68b0ed80,384). |
0 commit comments