New issue
Advanced search Search tips

Issue 701610 link

Starred by 1 user
Status: Assigned
Owner:
karandeepb@chromium.org
Cc:
rdevlin....@chromium.org
lazyboy@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Extension Doc Server: Wrong availability info. for some older extension APIs.

Project Member Reported by karandeepb@chromium.org, Mar 15 2017 
- Visit https://developer.chrome.com/extensions/api_index.
- Observe that many older APIs are available beginning Version 15. This is incorrect for some of the APIs.

This is related to https://omahaproxy.appspot.com/history.json?channel=dev&os=win&json=1 not serving information for older Chrome versions.

Comment 1 by rdevlin....@chromium.org, Mar 17 2017

Cc: karandeepb@chromium.org rdevlin....@chromium.org catmulli...@chromium.org lazyboy@chromium.org
For this, I think the right answer is that we should just stop showing the availability information after <n> releases (10 seems like it should be enough?  20 certainly should).  I don't think there's many valid reasons for wanting to know if an API was available in Chrome 39 in 2014, and, if you really want to, you can check the source history.

WDYT?  If this sounds good to y'all, lazyboy@ or karandeepb@, think you can take this?

Comment 2 by karandeepb@chromium.org, Mar 17 2017 

No info. is better than wrong info. so SGTM. 

But: I haven't dug into the relevant code (it is in branch_utility.py). The omahaproxy endpoint is used to fetch the branch from a version no. In case that fails, some logic steps in which causes the above bug. Do we even need the branch info? Don't think that is ever shown to the user.

Comment 3 by rdevlin....@chromium.org, Mar 24 2017

Cc: -karandeepb@chromium.org
Owner: karandeepb@chromium.org
Status: Assigned (was: Untriaged)
Assigning to karandeepb@ to get it out of triage.

Comment 4 by catmulli...@chromium.org, Feb 8 2018

Cc: -catmulli...@chromium.org
►

Sign in to add a comment