Publish minutes of 2025-05-22 meeting #834
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dotproto
approved these changes
May 28, 2025
Comment on lines
+23
to
+31
| * [Issue 832](https://github.com/w3c/webextensions/issues/832): Spec clarification: TabId 0 | ||
| * [Issue 831](https://github.com/w3c/webextensions/issues/831): Canonical header names | ||
| * [Issue 833](https://github.com/w3c/webextensions/issues/833): Side Panel API: query position: left/right, close(), and focus(): tab to and from side panel | ||
| * **Timely issues** (0 minutes) | ||
| * None | ||
| * **Check-in on existing issues** (5 minutes) | ||
| * [Pull 791](https://github.com/w3c/webextensions/pull/791): Add trial_tokens key to specification ([@oliverdunk](https://github.com/oliverdunk)) | ||
| * **Discuss nominated topics** | ||
|
|
There was a problem hiding this comment.
Move the topics that were added during the meeting to their own section.
Suggested change
| * [Issue 832](https://github.com/w3c/webextensions/issues/832): Spec clarification: TabId 0 | |
| * [Issue 831](https://github.com/w3c/webextensions/issues/831): Canonical header names | |
| * [Issue 833](https://github.com/w3c/webextensions/issues/833): Side Panel API: query position: left/right, close(), and focus(): tab to and from side panel | |
| * **Timely issues** (0 minutes) | |
| * None | |
| * **Check-in on existing issues** (5 minutes) | |
| * [Pull 791](https://github.com/w3c/webextensions/pull/791): Add trial_tokens key to specification ([@oliverdunk](https://github.com/oliverdunk)) | |
| * **Discuss nominated topics** | |
| * **Timely issues** (0 minutes) | |
| * None | |
| * **Check-in on existing issues** (5 minutes) | |
| * [Pull 791](https://github.com/w3c/webextensions/pull/791): Add trial_tokens key to specification ([@oliverdunk](https://github.com/oliverdunk)) | |
| * **Discuss nominated topics** | |
| * [Issue 832](https://github.com/w3c/webextensions/issues/832): Spec clarification: TabId 0 | |
| * [Issue 831](https://github.com/w3c/webextensions/issues/831): Canonical header names | |
| * [Issue 833](https://github.com/w3c/webextensions/issues/833): Side Panel API: query position: left/right, close(), and focus(): tab to and from side panel |
| * [oliver] Google I/O talks: https://groups.google.com/a/chromium.org/g/chromium-extensions/c/dRcCXIe4RlQ/m/R056FM6bAAAJ | ||
| * [mukul] Microsoft Build Announcements | ||
| [Simplified access to AI in Microsoft Edge: Introducing the Prompt and Writing Assistance APIs - Microsoft Edge Blog](https://blogs.windows.com/msedgedev/2025/05/19/introducing-the-prompt-and-writing-assistance-apis/) | ||
| [Issue 825](https://github.com/w3c/webextensions/issues/825): Inconsistency: Default content security policy |
There was a problem hiding this comment.
Suggested change
| [Issue 825](https://github.com/w3c/webextensions/issues/825): Inconsistency: Default content security policy | |
| [Issue 825](https://github.com/w3c/webextensions/issues/825): Inconsistency: Default content security policy |
| [Simplified access to AI in Microsoft Edge: Introducing the Prompt and Writing Assistance APIs - Microsoft Edge Blog](https://blogs.windows.com/msedgedev/2025/05/19/introducing-the-prompt-and-writing-assistance-apis/) | ||
| [Issue 825](https://github.com/w3c/webextensions/issues/825): Inconsistency: Default content security policy | ||
|
|
||
| * [rob] I have context. A while ago I suggested defaulting to HTTPs in extensions. Good way to help secure use data by transmitting it over secure connections. We've added upgrade requests by default to CSP. This could break some extensions if the backend doesn't support CSP. This creates an inconsistency where we're the only ones that enable HTTPS by default. Developers can easily opt out by specifying a custom CSP without `upgrade-insecure-requests`. |
There was a problem hiding this comment.
Suggested change
| * [rob] I have context. A while ago I suggested defaulting to HTTPs in extensions. Good way to help secure use data by transmitting it over secure connections. We've added upgrade requests by default to CSP. This could break some extensions if the backend doesn't support CSP. This creates an inconsistency where we're the only ones that enable HTTPS by default. Developers can easily opt out by specifying a custom CSP without `upgrade-insecure-requests`. | |
| * [rob] I have context. A while ago I suggested defaulting to HTTPS in extensions. Good way to help secure use data by transmitting it over secure connections. We've added upgrade requests by default to CSP. This could break some extensions if the backend doesn't support CSP. This creates an inconsistency where we're the only ones that enable HTTPS by default. Developers can easily opt out by specifying a custom CSP without `upgrade-insecure-requests`. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Generated from https://docs.google.com/document/d/1QkwhEMtMS67JBUkl_WVPZ4lRSKoWcQNlLJSf_GwSXg8/edit using the tool and process from #105.
During this meeting we discussed or mentioned issues #824, #531, #825, #830, #832, #831, #833, #693 and PRs #826, #791.