New issue
Advanced search Search tips

Issue 872062 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 14
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Feature



Sign in to add a comment

Consider removing Data Saver from Chrome for Android

Reported by soeren.s...@gmail.com, Aug 7

Issue description

Steps to reproduce the problem:
1. Enable Data Saver
2. After a couple of days: Check the amount of data saved
3. Find out that it didn't actually save much data due to the fact that the web is now mostly accessed via HTTPS/TLS.

What is the expected behavior?

What went wrong?
With more and more sites making the switch to TLS, the Data Saver built into Chrome for Android becomes redundant. Personally, I can see a steady decline in the amount of data saved and recently went below 3% of data saved within the last month. That is way less than what I used to get and not worth mentioning.

I'm suggesting to consider removing the Data Saver from Chrome for Android to reduce maintenance and the code base.

Did this work before? N/A 

Chrome version: 68.0.3440.84  Channel: stable
OS Version: 8.1
Flash Version:
 
Labels: Needs-triage-Mobile
Cc: chelamcherla@chromium.org
Components: Internals>Network>DataProxy
Labels: Target-70 M-70 Triaged-Mobile FoundIn-70
Status: Untriaged (was: Unconfirmed)
As per comment#0 this seems to be a feature request. Hence marking as Untriaged for further inputs from dev team.

Thanks!
Status: WontFix (was: Untriaged)
Engineers on Data Saver are aware of the shift towards more widespread use of HTTPS, for which intermediary transcoding techniques can't be used to reduce data use. However, we are working on a number of features to reduce data use on HTTPS that don't involve proxy-based recompression of resources.

Sign in to add a comment