Hello Chromium Extensions Team,
I have a question regarding the desktop_android feature and the roadmap for Chrome Extension API support on that platform.
As I understand it, desktop_android is intended to bring desktop-class browsing capabilities to Android, and extension support is a key part of achieving feature parity with desktop Chrome. However, while reviewing the current state, it appears that a significant subset of Extension APIs (e.g. parts of tabs, windows, sessions, tabGroups, etc.) are still not fully supported or are partially implemented on desktop_android.
Could you please clarify:
Is there an official roadmap or milestone for when desktop_android aims to support the full set of desktop Chrome Extension APIs?
Are there specific APIs or categories that are explicitly planned, deferred, or out of scope for desktop_android?
Is the current approach to extension support on desktop_android expected to converge with desktop Chrome’s implementation, or will there be long-term structural differences?
Are there public design docs, tracking bugs, or feature flags that describe the planned rollout phases for extension API coverage on desktop_android?
Understanding the long-term direction would be very helpful for teams evaluating extension compatibility and planning development and testing strategies around desktop_android.
Thank you for your time and for any guidance you can share.