Invoke TriggerManager()->StartCollectingThreatDetails() with a proper HistoryService |
|||||||||
Issue descriptionStartCollectingThreatDetails() takes a HistoryService as a parameter. Creating a proper HistoryService is not as straightforward though because currently the HistoryServiceFactory lives in the chrome/ layer and relies on Profile which we don't have in Android WebView. Figure out a way to solve this..
,
Jun 9 2017
,
Jun 16 2017
,
Oct 11 2017
,
Nov 10 2017
,
Feb 18 2018
,
Sep 17
Looks like this is still unresolved: https://cs.chromium.org/chromium/src/android_webview/browser/aw_safe_browsing_blocking_page.cc?l=74&rcl=0e9cb2681888d293a4a5e12cdd51e9bf4991a620 Safe Browsing team: how important is this to implement? Have we started any docs on how to implement this?
,
Sep 17
,
Sep 17
,
Sep 19
IIRC the chrome safe-browsing team was planning to eliminate/refactor the HistoryService completely.. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by timvolod...@chromium.org
, Jun 9 2017