Using the per-revision bisect providing the bisect results,
Good build: 59.0.3056.0 (Revision: 460603).
Bad build : 59.0.3057.0 (Revision: 460966).

You are probably looking for a change made after 460645 (known good), but no later than 460646 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/174eb44312202a5132de900553f7c302da0feef6..85bab14c835935e79a0b63f24b47f671840373de

@erikchen: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.
Adding RB Label as this is a recent Regression. Please remove if not required.
Thank You.

Still we are able to reproduce the issue on Mac-10.12.4 using chrome version 60.0.3073.0.
@erikchen could you please look into this issue.

Thanks.

erikchen@ Since this issue is marked as RB-Stable can we get any latest update available on this issue?

Thanks!

Tested this issue on Android 7.0.99; Build/MRA20 using chrome version #59.0.3065.0 by following steps mentioned below.

1.Launched chrome and navigated to http://timesofindia.indiatimes.com/
2.Scrolled down till the video page and clicked on video
3.Observed the video buffers for longtime and no video is displayed to check this issue

Tested the same on mobile site m.timesofindia.com and observed able to play the videos in full screen with no issues.

foolip: This seems likely to be the same fullscreen issue that we observed before? What's the status of the blink fullscreen refactor?

The feature in question is still experimental, so this shouldn't affect Chrome stable. Have you observed otherwise?

#13, I'm currently working on  issue 402376 , specifically on updating https://fullscreen.spec.whatwg.org/ with a bunch of changes into something that would allow it to be relanded without causing the same regressions as last time.

Since my changes weren't in the regressions range, assigning back.

Reminder that M59 Stable is launch is coming soon (less than 2 weeks)! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP so it gets enough baking time in Beta (before Stable promotion). Thank you!

erikchen@, foolip@ - If this is part of an experiment, can we remove RB-Stable label? (we're about a week away from M59 stable) 

The CL that causes this issue is for a feature that has status=experimental
https://codereview.chromium.org/2743053003/diff/280001/third_party/WebKit/Source/platform/RuntimeEnabledFeatures.json5

So it shouldn't be RB-S. This problem [should] be fixed by the new fullscreen implementation.

Can we close this now that 402376 has been resolved?

Yes, closing as Invalid.