Move concept of dangerous downloads out of //content |
||
Issue description//content shouldn't care about what it means for a download to be dangerous. Infact this concept now lives entirely in //chrome. Handling of dangerous download file types should also likewise be a concept entirely native to //chrome.
,
Apr 5 2018
the concept is not in download/, mark this as deprecated, although we still need to investigate whether we can remove dangerous from download/ |
||
►
Sign in to add a comment |
||
Comment 1 by sheriffbot@chromium.org
, Jul 18 2017Status: Untriaged (was: Available)