Agenda discussion for public meeting on 2022-11-10

[carlosjeurissen]

Link to previous Agenda discussion (2022-10-27): Issue 297

List of topics to discuss (In order)

Mentioned people are those who can introduce the topics.

Existing pull requests

Discuss merge of PR
Pull request 291: Document How we work

Housekeeping

Discussing status on IDL sharing

@hanguokai @carlosjeurissen Adding three new labels: breaking-change, topic: localisation, topic: action
Issue 244c: Better status labels for issues

@oliverdunk Should discussing existing issues have priority over newly created issues

Quick issue check-ins

Check-in on support for runtime.getFrameId()
Issue 12: request: allow to retrieve a frameID from an <iframe> element

Check-in on support for replacing contextMenus with menus and (2) changing the API signature of menus.create / contextMenus.create
Issue 188: Inconsistency: Permissions "menus"

Check-in on support for declaring bg scripts in a neutral way
Issue 282: Proposal: declaring background scripts in a neutral way

@Rob--W @oliverdunk action.openPopup / browserAction.openPopup
Issue 15: Discuss and encourage adoption of browserAction.openPopup()
Issue 160: Ensure consistency of action.openPopup API across browsers

New issues

@hanguokai browser.commands issues (Previously Issue 300)
Issue 308: New api: shortcut changed event
Issue 309: Unify the format of Command.shortcut or add a new Command.shortcutKeys property
Issue 310: New API: Open Shortcut Setting

@carlosjeurissen discuss and clarify the proposal
Issue 304: Automatically grant https: host_permissions with http:

@carlosjeurissen request to discuss this offline
Issue 306: scripting.InjectionTarget.worker property to inject WorkerScope(s)

@NV @oliverdunk Discuss extension UI on top of tabs and how to implement it, on mobile as well
Issue 307: Proposal: extend extend browser.action API to display popover in the middle of the screen
Issue 235: Discuss allowing extensions to reliably draw over pages

@tophf @carlosjeurissen discuss proposal and check-in on support
Issue 311: Ability to unload the background script from SW code [regression from MV2]

@tophf Discuss changing registerContentScripts api names and their deprecation track
Issue 313: registerContentScripts misleadingly names page scripts as content scripts

@erosman @carlosjeurissen Discuss allowing to optionally delay killing popup page for max 30 seconds to finish scripts after the popup got closed
Issue 315: Proposal: Complete privileged page process even after closing

@hanguokai Discuss proposal and check-in on support
Issue 312: [contextMenus] create or update contextMenus in a single call

@hanguokai
Issue 317: registerProtocolHandler (protocol_handlers) in extensions

@ameshkov @105th Discussing DNR rules and ruleset limits
Issue 318: Adjust the maximum number of static rulesets and enabled rulesets
Issue 319: Increase the maximum number of dynamic rules to 30,000
Issue 162c: Declarative Net Request proposal: disable individual static rules

Ongoing issues in need for discussion

@hackademix discuss scripting.registerContentScripts
Issue 103: Use cases and features for registerContentScripts() (early conf, parameters, WorkerScope injection, tab filtering, CSP)

@dotproto Discussing default content_security_policy
Issue 98: Inconsistency: Default content_security_policy

@carlosjeurissen Continue CSP reporting conversation
Issue 97: Proposal: replacement for deprecated report-uri for content_security_policy
Issue 197: feature request: content_security_policy_report_only in manifest.json

@bershanskiy Discuss proposal and check-in on support
Issue 40: Provide consistent access to browser.permissions API in the devtools

@regseb @carlosjeurissen See if we can agree on resolving the inconsistency
Issue 86: Standardize storage.onChanged event when you set the same values.

@twschiller Discuss proposal and check-in on support
Issue 19: request: APIs and infrastructure to simplify cross-browser automated testing of extensions

@bershanskiy Discuss proposal and check-in on support
Issue 138: Proposal: lLet content scripts listen for event chrome.runtime.onUninstalled

@tophf
Issue 293: Transfer huge binary data buffer between service worker and content script instantly

@bershanskiy
Issue 294: Proposal: one-time message passing addressed to a specific documentId or contextId

@hanguokai
Issue 298: Clarification: Deprecation Policy for Browser Extensions

@ghostwords
Issue 302: Blocking webRequest use case: DNR unable to properly redirect based on URL parameters

@Rob--W
Issue 303: Default to using https for requests from extensions, e.g. via CSP

@carlosjeurissen Confirm if WRITE-methods are by definition handled with a queue
Issue 292: Inconsistency: StorageArea callback order

@ghostwords
Issue 227: Making host permissions optional by default appears to be harmful for extensions with global host permissions

Discuss support for i18n.getLanguageDictionary vs i18n.getMessage with locale option
Issue 274: Proposal: i18n.getLanguageDictionary

@jonathanKingston
Issue 284: Main world User Script shared params

@carlosjeurissen Check-in support for deprecating options_page
Issue 108: Deprecate options_page manifest property

New issues backlog

@kiaraarose
Issue 316: tabs.getCurrent() returns undefined when being called from the popup

[oliverdunk]

#299: Performance Tracking for Extension Service Workers

This one is closed as unactionable, should we remove it from the agenda?

[dessant]

@carlosjeurissen, would it be possible to add this question to the agenda?

There does not seem to be any documentation about how already granted permissions are handled in existing installations during an MV2 to MV3 update in Chrome and Firefox, and it would be important to know if existing users will need to take an action after the update.

[ameshkov]

@carlosjeurissen hi, can these questions be added to the agenda?

• Increase the maximum number of dynamic rules to 30,000 #319
• Adjust the maximum number of static rulesets and enabled rulesets #318
• Declarative Net Request proposal: disable individual static rules #162 (comment)

[erosman]

@erosman Discuss allowing to optionally delay killing popup page for ~30 seconds after it got closed

The proposal was not time based. The intention is to complete the execution of user-action process and then discard the page. I would imagine that could take a few milliseconds in most cases, to a few seconds (no way close to 30 seconds).

[carlosjeurissen]

@erosman Thanks for the clarification! Updated to match your comment. Will you attend the meeting to talk about the proposal?

[erosman]

@erosman Thanks for the clarification! Updated to match your comment. Will you attend the meeting to talk about the proposal?

Unfortunately, I wont be able to. 😞
However, I am around if there is a need for clarification.
I have also added some examples to the original topic.

[dotproto]

Closing this issue as today's meeting will begin in just a few minutes.

[NV]

@NV @oliverdunk Discuss extension UI on top of tabs and how to implement it, on mobile as well
Issue 307: Proposal: extend extend browser.action API to display popover in the middle of the screen
Issue 235: Discuss allowing extensions to reliably draw over pages

I couldn't attend this time, but by looking at the public notes, it looks like the topic wasn't discussed anyway. I'll attend the next public meeting.

[hanguokai]

@NV I attended the meeting for the first time. Because the meeting time is limited to one hour, there are many topics, more than half of the issues were not discussed. I think that the most efficient way of discussion is asynchronous discussion on the issue. But attending meetings can get more attention from browser vendors, who usually don't have enough time to read and think about every issue in detail.

@oliverdunk Thank you for getting started implementing return "_execute_action" command and #308 .