Hi,
My extension uses the TabCapture API to modify the tab's audio. Once the tab's audio is captured, the user cannot enter fullscreen, only partial fullscreen. This issue was reported here (
https://issues.chromium.org/issues/41385421).
To work around this, I'm implementing a fullscreen shortcut that...
1. Turns off tabCapture temporarily.
2. Enters fullscreen.
3. Turns tabCapture back on.
However, I'm concerned this might violate the store's program policies. As mentioned
> Any attempt to circumvent intended limitations or enforcement actions will result in the immediate termination of your developer account, and possibly related developer accounts.
It's not clear whether the fullscreen issue is an intended limitation or a bug (Issue mentioned above has been open for years). If it's a intended limitation of the TabCapture API, I do not see it mentioned anywhere.
Will this shortcut be a violation of this policy?