Perhaps it would help with user inquiries around extension compatibility if there were a table that described the amount of WebExtensions API support in Orion that sorta looks like Kangax's famous per browser ECMAScript support table.
4
Establish a Separate Dashboard or Table for WebExtensions API Support
Vlad added the Clarification tag .
Vlad By the development team, bandwidth permitting, given you know which interfaces are and are not supported at release. I'm aware you've implemented behavior that alerts beta users whenever an extension attempts to call an unsupported method.
Perhaps such a table would be more useful when the browser is eventually open-sourced and possible contributors can act on the information in this table to find potential contributions.
- Edited
b3noit Development team has negative bandwidth. There are over 1,300 issues on this board, just managing them gets us in position of negative bandwidth, let alone fixing them.
Each extension would need to be manually checked. There are over 100,000 extensions and each extension update and Orion update can change status. It is beyond impossible to do it in the way you suggested.
- Edited
Vlad Maybe we were miscommunicating at a certain level as it appears you already have what I had in mind here https://browser.kagi.com/WebExtensions-API-Support.html
If I'm reading this table right and it's up-to-date
Full support for almost everything but certain extensions still don't work?
No one is typing