[Chrome][Android6.0.1][51.0.2704.77] Download policy request (download via DownloadManager or download via Chrome)
Reported by
seiyon.p...@gmail.com,
Jun 10 2016
|
||
Issue descriptionSteps to reproduce the problem: 1. Precondition : Chrome 51.0.2704.77 2. Launch Chrome 3. Connect to "http://125.141.31.138/w/@LGE-TEST/download/oma-download.html" 4. Click link (Content is downloaded via DownloadManager) 5. Touch and hold the link to choose 'Save Link' (Chrome crashes) 6. Launch Chrome again 7. Connect to "http://125.141.31.138/w/@LGE-TEST/download/oma-download.html" again. 8. Click link (Content is downloaded via Chrome itself) What is the expected behavior? Contents should be downloaded via DownloadManager. What went wrong? Download policy is not consistent. Normally contents are downloaded via DownloadManager. But once Chrome crashes, contents are downloaded via Chrome. Did this work before? N/A Chrome version: 51.0.2704.77 Channel: stable OS Version: 6.0.1 Flash Version: Shockwave Flash 21.0 r0 I'd like to know Chrome download policy plan. Policy will be "downloading via DownloadManager" or "downloading via Chrome".
,
Jun 10 2016
the crash was fixed in M52, you can try the beta to verify it. There is no requirement that download has to go through Andorid DownloadManager. And Android Downloadmanager is going to be deprecated soon.
,
Jun 14 2016
I have questions about "Android Downloadmanager is going to be deprecated soon" 1. Deprecation plan When will Android Donloadmanager be deprecated? N OS? or next N OS? 2. Download policy Will contents be downloaed via app itself if Android Donloadmanager is deprecated? For example, 3rd party browser apps should download contents for themselves not using Downloadmanager?
,
Jun 14 2016
Deprecation of Android DownloadManager doesn't rely on android version, but depending on the chrome version. Current plan is M52 or M53, depending on user feedback. Only Chrome starts to stop using DownloadManager in most cases. Other apps can still use Android DownloadManager.
,
Jun 17 2016
Feature request about downloading policy is : 1. Unsupported mime-type contents should be handled by DownloadManager regardless of Chrome's policy change. 2. DRM contents should be handled by DownloadManager regardless of Chrome's policy change. Request reason is : Only DownloadManager can encrypt and decrypt DRM contents properly. Hence to support DRM contents, they should be handled by DownloadManager not Chrome.
,
Jun 17 2016
What is the reason for 1? DRM contents will still go through DownloadManager after the change.
,
Jun 20 2016
My assumption is that Chrome will download DRM contents using Chrome if Chrome starts to stop using DownloadManager in most cases. That's the reason why I requested to download DRM contents via DownlaodManager. According to comment #8, DRM content is not the case of "most cases" and DRM contents will still go through DownloadManager after the change. Hence I'd like to rule out the first request from my feature requests.
,
Jun 21 2016
I have one more question about DRM contents. Could you clarify "OMA Download Descriptor (OMA DD)" case? Will "OMA Download Descriptor (OMA DD)" also go through DownloadManager after the change like DRM contents? Thanks.
,
Jun 21 2016
No, DD file will be downloaded using chrome network stack, after extacting the url from DD, the DRM file will be downloaded by DownloadManager. |
||
►
Sign in to add a comment |
||
Comment 1 by svaldez@chromium.org
, Jun 10 2016Components: UI>Browser>Downloads
Labels: Needs-Feedback
Status: Available (was: Unconfirmed)