Remove shutdownSafeBrowsing method |
||||
Issue descriptionAfter some discussion on http://ag/2743990 and conversation with the SafetyNet team, we decided that it doesn't make sense to expose shutdownSafeBrowsing in our public API. A brief summary: * If we did expose shutdownSafeBrowsing(), when would apps call it? There's no signal for an application crash/death. * As we shift toward the connectionless API, the current thought is to intentionally never shutdown Safe Browsing (so the database will almost always be ready). shutdownSafeBrowsing API is counter intuitive to this.
,
Aug 23 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/clank/internal/apps/+/3936d4fb2c261895040003fee2bfb353339df6b8 commit 3936d4fb2c261895040003fee2bfb353339df6b8 Author: Nate Fischer <ntfschr@google.com> Date: Wed Aug 23 21:59:35 2017
,
Aug 23 2017
No QA verification needed.
,
Oct 11 2017
,
Aug 24
Bulk edit: marking stale 'fixed' bugs as 'verified' since they don't need verification at this point. |
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Aug 23 2017