|
|
|
|
|
by dotproto
1030 days ago
|
|
> the extension APIs are standardised enough that this is actually possible a lot of the time A bit off topic, but as a co-chair of the WebExtensions Community Group[1] (WECG) I'm a bit touchy about the calling WebExtensions "standardized." A few years back the Browser Extensions Community Group[2] created a spec for WebExtensions, but it never reached a state that we'd normally refer to as a web standard. (Technically W3C community groups can only produce "Reports" and these documents are not on the standards track.[3]) FWIW, I'm very bullish about specifying and (hopefully) standardizing the WebExtensions platform. I'm especially excited about having a good chunk of dedicated time to sit with browser folks at TPAC 2023[4] and try to work out some open questions about where we're going and how we're going to get there. [1]: https://github.com/w3c/webextensions/
[2]: https://browserext.github.io/
[3]: https://www.w3.org/community/about/faq/
[4]: https://www.w3.org/2023/09/TPAC/ |
|