New site is missing API version information about developer.chrome.com

[samthor]

Thanks for the bug report. We found that the vast majority of API versions in the old site were set incorrectly to 38 (everything without correct data was set to this). There were a handful of more up to date APIs and we will be bringing version information back for things introduced in the past couple of years (38 won't be included, as it was from 2014) once we can identify what was recently changed, and we hope to have this information up in the coming days.

…

On Wed, 9 Dec 2020, 23:56 Jackie Han, ***@***.***> wrote: I found there is no "Since Chrome *version*" in new api reference. In the past, there are many statement say like "Since Chrome 48". This information is useful for compatibility. Developers can detect features or set "minimum_chrome_version" in manifest. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#39>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA5DECIXGKA3LJYN3D7JO3ST5XX3ANCNFSM4UTOLMJQ> .

[tophf]

for things introduced in the past couple of years

There was just a handful of changes in the extensions API over the past couple of years so if that's your threshold we will lose all the info from the past ~8 years of development like the one below for chrome.tabs API. It's understandable that Chromium/Google supports only the current stable version but this info is helpful for us extension authors as we often keep our extensions compatible with older versions of Chrome.

[dotproto]

I took the liberty of updating the issue title to reflect the observed bug rather than describing a feature request.

[hanguokai]

I hope this issue can increase the priority, because it affects the experience to all developers.

[tconfrey]

Adding my two cents. In my experience this is more serious than just 'Since' or 'Deprecated' for specific arguments or methods.

The main API Reference page lists 'Stable' APIs while also having Beta and Dev sections. 'tabGroups' is shown under Stable and nowhere else, but I have found that that whole API is not available on the Stable channel. Similarly the 'group' method on 'tabs' is not available on Stable.

This is a pretty big gap between advertised and available functionality! The site is not just missing api version information it's explicitly giving the wrong information.

How can I find out when tabGroups will be available via API?

[samthor]

Please take a look at #364 if you're curious about how we're going for a fix.

https://deploy-preview-364--developer-chrome-com.netlify.app/ is its staging URL.