Agenda discussion for public meeting on 2022-10-27

[carlosjeurissen]

Since our last meeting 2022-10-13 was lacking topics to discuss. It seems it makes sense again to start listing down topics to discuss in the next meeting. Below is a collection of new issues, old issues not yet discussed, and follow-up issues.

For the next meeting, not all of these topics need to be discussed. If we do not finish all of them, we can simply move them to the next meeting. Let me know if the order with the issues should be changed. The fact some issues are new does not necessarily have to mean they should be discussed first.

List of topics to discuss

Existing pull requests

Publish minutes of 2022-10-13 meeting
#290

Document How we work
#291

Housekeeping

Discussion on deliverables and associated work.

Adding three new labels: breaking-change, topic: localisation, topic: action
#244 (comment)

Quick issue check-ins

runtime.getFrameId()
#12

Permissions "menus"
#188

Neutral background script definition
#282

New issues

Inconsistency: StorageArea callback order
#292

Transfer huge data blobs between service worker and web pages instantly
#293

Proposal: one-time message passing addressed to a specific documentId or contextId
#294

getBackgroundPage
#295

i18n.getMessage() language fallback paths
#296

Clarification: Deprecation Policy for Browser Extensions
#298

Performance Tracking for Extension Service Workers
#299

_execute_action command
#300
#301

Blocking webRequest use case: DNR unable to properly redirect based on URL parameters
#302

Default to using https for requests from extensions, e.g. via CSP
#303

Ongoing issues in need for discussion

action.openPopup / browserAction.openPopup
#15
#160

Drawing over pages
#235

scripting.registerContentScripts
#103

APIs and infrastructure to simplify cross-browser automated testing of extensions
#19

deprecate i18n.getAcceptLanguages
#107

Provide consistent access to browser.permissions API in the devtools
#40

Default content_security_policy
#98

Standardize storage.onChanged event when you set the same values.
#86

Deprecate options_page manifest property
#108

Let content scripts listen for event chrome.runtime.onUninstalled
#138

CSP reporting
#97
#197

[oliverdunk]

Thanks for opening this!

action.openPopup / browserAction.openPopup

Appreciate you adding this one. I'm still working on a patch to Firefox and I'm tentatively hoping it might be merged by the next WECG. I think input from Google on their timeline and both Google and Apple on the proposed behaviour would also be great.

I'd also love to add #235. I brought this up in a Modern UI AMA Google were doing on Twitter and @jh3y sounded interested in discussing this more generally. I'm not sure if I'll have it done by the next meeting but my plan was to open some issues in other WG repos and see if we can start some discussion.

[hackademix]

I'd like to revisit #103, and especially "Script Injection in WorkerScope", a topic discussed exactly one year ago, which the group was apparently quite supportive of but AFAIK didn't actually go anywhere.

[dotproto]

Thanks for opening this, @carlosjeurissen!

[Rob--W]

@carlosjeurissen Instead of changing the title, could you open a new issue? Then the topic can represent the agenda at the time that the issue was filed, which makes it easier to track historical changes.

[carlosjeurissen]

@Rob--W This crossed my mind when recycling the issue. Since there are many topics still up for discussion and the majority of the ones specified will be moved to the next meeting it only felt natural to recycle this. As for historical changes, we have the Public Notes for this right?

[Rob--W]

This issue is linked as the proposed agenda from the past meeting. Every "agenda" issue should be associated with only one meeting.

Since we haven't really used this issue to populate the agenda, I'm not against recycling this, but for next time let's close and create new issues.

If you want to make this easier to use, could you use the template for the meeting notes? Then it can be copy-pasted.

* [Issue 1234](https://github.com/w3c/webextensions/1234): Exact title of issue here
* Etc.

[carlosjeurissen]

@Rob--W In that case having separate issues makes sense. This issue has been reverted to its original state and has been closed. A new agenda discussion has been opened here:
Issue 314

Also started changing the Issue link format. Good suggestion!