Tested in chrome # 56.0.2924.87 and 58.0.3020.0 on win 10.0 & 7 and not able to reproduce the issue.Please find the screen cast for your reference.

@ loorongjie: Could you please let me know if i have missed anything and if possible, Please create new profile without extensions and apps.Re-check once and let us know the observation of the issue which would help us to triage the issue further.

Thanks in Advance.

Deleted: 693391.mp4 2.3 MB

	693391.mp4 2.3 MB View Download

Screencast in #2 is working as intended.

I seem to have found the root cause:
- chrome.exe --user-data-dir="new folder": works
- remove Chrome User data folder and restart: works
- connect to Google Account: fail
- connect to Google Account (incognito): fail
- connect to Google Account, disable Chrome Data Saver (all other extensions remain on): works

Tested with Chrome 56.0.2924.87 and 58.0.3020.0 on Windows 10

Can you install Chrome Data Saver and try again?

Thank you for providing feedback. removing "Needs-Feedback" label.

loorongjie@ - Thanks for more update...!!

Able to reproduce the issue on Windows 10, Mac 10.12.3 and Ubuntu 14.04 using chrome reported version #56.0.2924.87 and latest canary #59.0.3035.0.

Bisect Information:
=====================
Good build: 53.0.2774.0  Revision(400850)

Bad Build : 53.0.2777.0  Revision(401526)

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/ebc003f5a6e243e85e0773dbbd32cdfacf27d152..db76dca1c825e5c60646ac465cce7ddc900712ac

From the above change log suspecting below change

Review url: https://codereview.chromium.org/2071793003

mlamouri@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks...!!

It has been 20 days now, have we identified the offending commit(s)? Or this is already being worked on internally?

@mlamouri : Is there any timeline for this fix ?

I'm afraid I'm not the right person to look into this.

I spoke too quickly. I didn't properly parse comment #3. Data Saver is indeed the likely reason of this breakage.

So far, this is working as intended. However, we are re-considering this decision. +dahlke@ +mdw@ FYI

Hi there, I don't quite understand what's happening here and how Data Saver is implicated. Adding bengr@ and buettner@ for review.

Given the bisect results, only one change has anything to do with Data Saver. That change uses Data Saver information to decide whether to preload.

See: https://bugs.chromium.org/p/chromium/issues/detail?id=620755

Ping. I know Chromium engineers are busy with other bugs, but can I get an update on current progress for this one?

This is working as intended. Preloading of HTMLMediaElements is disabled when Data Saver is enabled. Note that it seems from the offending CL that Chrome has the same behavior on cellular connections even when Data Saver is disabled. 

Re-assigning to aposner@ to reconsider the product decision.

Jon, can you share the latest on your proposal to change autoplay behavior, including for Data Saver users?

So this means Data Saver will implicitly break Google voice for Speech Synthesis and no one is going to warn about this in Data Saver's Chrome Web Store page?

Based on the last conversation we had, the plan is to remove autoplay blocking for data saver users for the very reason that it breaks sites without users having the ability to associate or control the behavior. The plan was to do that when 1.) the new policy was rolled out and 2.) we had the telemetry in place to measure its impact on overall page size. 

aposner@, I will send the policy via email.

dahlke/bengr, is there an update on this?

Refreshed during triage.