Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WECG at TPAC 2024 #659

Closed
xeenon opened this issue Jul 17, 2024 · 9 comments
Closed

WECG at TPAC 2024 #659

xeenon opened this issue Jul 17, 2024 · 9 comments
Labels
admin Administrative tasks associated with organizing and conducting the group's work agenda Discuss in future meetings

Comments

@xeenon
Copy link
Collaborator

xeenon commented Jul 17, 2024

The W3C will be holding TPAC 2024 in Anaheim, CA, USA on September 23-27. This thread will serve as our primary discussion area for planning and scheduling purposes.

Schedule:

Coordination: https://github.com/w3c/webextensions/wiki/TPAC-2024-Coordination

@github-actions github-actions bot added needs-triage: chrome Chrome needs to assess this issue for the first time needs-triage: firefox Firefox needs to assess this issue for the first time needs-triage: safari Safari needs to assess this issue for the first time labels Jul 17, 2024
@xeenon xeenon added agenda Discuss in future meetings admin Administrative tasks associated with organizing and conducting the group's work and removed needs-triage: chrome Chrome needs to assess this issue for the first time needs-triage: safari Safari needs to assess this issue for the first time needs-triage: firefox Firefox needs to assess this issue for the first time labels Jul 18, 2024
@dotproto
Copy link
Member

I created the TPAC 2024 Coordination page on our repo's wiki to help coordinate our in-person activities.

@dotproto
Copy link
Member

dotproto commented Aug 1, 2024

In today's meeting we briefly discussed some ides for what we should discuss or work on at TPAC. Ideas raised included:

  • WebExtensions integration into Web Platform Test
    • Primary: Get tests running in Chrome, Firefox, and Safari
    • Secondary: Start building out test suites for APIs
  • Check notes from San Diego F2F for topics
  • Specification work
  • Browser namespace
  • API inconsistencies and alignment

@xeenon
Copy link
Collaborator Author

xeenon commented Aug 5, 2024

I'd like to discuss postMessage and possible replacement options (#77, #78).

@xeenon
Copy link
Collaborator Author

xeenon commented Aug 15, 2024

We would also like to discuss declarative cosmetic rules (#362) and plan to bring a proposal to go over.

@ameshkov
Copy link

Will there be an option to connect remotely?

@dotproto
Copy link
Member

dotproto commented Sep 3, 2024

@ameshkov, there should be. The TPAC site describes the event as a hybrid meeting. Our calendar on the W3C site doesn't currently have meeting info, but I'll try to make sure that those events have video conferencing info on the day of the event.

@Rob--W
Copy link
Member

Rob--W commented Sep 16, 2024

I'd like to talk about (storage) partitioning in extension APIs, including:

@hanguokai
Copy link
Member

I won't attend this meeting. However, I suggest that in addition to specific technical issues, you can also discuss some meta issues about the ecosystem. For examples:

  1. What are the biggest obstacles to browser extensions?
    a) Browsers are already too complex and the development cost is high b) There is a lack of internal human resources and few external contributors.

  2. Security and Privacy: Design, Permissions Models, Web Store Reviews and Enforcements.

  3. Developers Success: Business Model, User Experience and Compliance Issues.

@carlosjeurissen
Copy link
Contributor

carlosjeurissen commented Sep 20, 2024

  1. Some of the i18n related topics which have been on the shelve for some time being:
  1. The issue on embedding pages we also talked about during the San Diego meeting:
    Proposal: API to embed pages in WebExtension bypassing CSP #483

  2. Recently opened issue related to extension ui sizing. Discussing this during TPAC could be beneficial considering https://github.com/w3c/csswg-drafts folks being present as well:
    Addressing auto-sizing of extension UI (options, popup, sidepanel) #692

  3. Getting the associated tab id from an extension popup:
    tabs.getCurrent() returns undefined when being called from the popup #316 (comment)

  4. A number of other issues we can make progress on:
    Proposal: Add filter for DNR modifyHeaders #439

@hanguokai very much agree on talking about compliance/permission models / webstore reviews and enforcement. While many of them have historically been out of scope for this group. I see a lot of value in streamlining across browsers and extension stores. We are in an awkward situation in which certain manifest files can load a browser but not accepted in a store and the reverse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
admin Administrative tasks associated with organizing and conducting the group's work agenda Discuss in future meetings
Projects
None yet
Development

No branches or pull requests

6 participants