Visit on Github.
This issue was created because the 'horizontal review requested' label was added to § https://github.com/w3c/strategy/issues/146
This review is requested prior to the Advisory Committee Review.
New charter proposal, reviewers please take note.
Charter
diff from charter template
Expected end of charter refinement phase: second half of September
(CG) chair dashboard
What kind of charter is this? Check the relevant box / remove irrelevant branches.
This came from the WebExtensions CG itself. Given the wide market for browser extensions, outreach could be large...
This will significantly increase our work area, in particular in horizontals: a11y, security, and privacy. Those experts are already stretched...
cc @xeenon @dotproto
The Web Extensions draft spec has been developed in a W3C CG Browser Extension CG and is being implemented but not harmoniously, apparently.
Why isn't there a Working Group for this work and what is the REC track plan for Web Extensions? Or, what's the alternative to this spec?
cc @plehegar
Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1138
OpenedAug 15, 2025
This issue was created because the 'horizontal review requested' label was added to § https://github.com/w3c/strategy/issues/146
This review is requested prior to the Advisory Committee Review.
New charter proposal, reviewers please take note.
Charter Review
Charter
diff from charter template
Expected end of charter refinement phase: second half of September
(CG) chair dashboard
What kind of charter is this? Check the relevant box / remove irrelevant branches.
Communities suggested for outreach
This came from the WebExtensions CG itself. Given the wide market for browser extensions, outreach could be large...
Known or potential areas of concern
This will significantly increase our work area, in particular in horizontals: a11y, security, and privacy. Those experts are already stretched...
Anything else we should think about as we review?
cc @xeenon @dotproto
The Web Extensions draft spec has been developed in a W3C CG Browser Extension CG and is being implemented but not harmoniously, apparently.Why isn't there a Working Group for this work and what is the REC track plan for Web Extensions? Or, what's the alternative to this spec?Charter facilitator(s)
cc @plehegar
<!-- Content below this is maintained by @w3c-tag-bot -->Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1138