Add remove, edit, create api to chrome.topSites
Reported by
han.guo...@gmail.com,
Dec 28
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce the problem: None What is the expected behavior? Add remove, edit, create api to chrome.topSites. https://developer.chrome.com/extensions/topSites What went wrong? Chrome default new tab page now can remove/edit/create topSites by users, but chrome.topSites api still only has get api, no remove/edit/create api. WebStore page: Did this work before? No Chrome version: 71.0.3578.98 Channel: stable OS Version: OS X 10.13.6 Flash Version: chrome.topSites extension api is useful for custom new tab chrome extension. Compared to bookmarks, topsites are from statistics, that is useful for users. But sometimes user want to remove a topsite. For the same reason, it's useful for chrome extension to have the ability to remove a topsite.
,
Dec 31
chrome.topSites simply reports the most visited URLs from the browsing history [1], so the only inherently possible way to change the output of chrome.topSites.get is to actually alter the history, for example by using chrome.history API. [1]: https://cs.chromium.org/chromium/src/chrome/browser/extensions/api/top_sites/top_sites_api.cc?l=30-31&rcl=6ac58aca
,
Dec 31
Thanks. I just tried chrome.history.deleteUrl(aTopSiteUrl) , then that topSite from chrome.topSites.get was also disappeared. Great! I only need this api to remove a topSite. I suggest chrome.topSite api doc add a paragraph for removing a topSite by chrome.history api. create and edit topSite are not very meaningful.
,
Jan 4
As per comment#0 the issue seems to be a feature request, hence marking it as untriaged and requesting someone from dev team to look into the issue. Thanks.!
,
Jan 4
Marking as available for now. In the meantime, if someone wants to try to implement this themselves, please follow https://chromium.googlesource.com/chromium/src/+/master/extensions/docs/new_api_proposal.md |
|||
►
Sign in to add a comment |
|||
Comment 1 by swarnasree.mukkala@chromium.org
, Dec 31