The website doesn't seem to exist. Was this a typo?

Sorry for a typo.
URL should be http://sports.media.daum.net.

I can reproduce this in Stable indeed but Chrome Beta/Dev/Canary all seem to work fine. Do you confirm?

It is also reproducible on beta(v60)/dev(v61).

Thank you for providing more feedback. Adding requester "candrada@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

dknandiraju@, can you repro?  Thanks.

1) Issue is reproducible from all builds of M55 to M60 play store build, Please find logs and video taken on Moto G4 Plus(athene_f)/7.0.0 on M60 @ http://go/chrome-androidlogs1/6/746147-m60
2) On M61 a white blank screen appears on following steps to reproduce the issue, Please find logs and video taken on Moto G4 Plus(athene_f)/7.0.0 @ http://go/chrome-androidlogs1/6/746147-m61
3) This issue is not reproducible on latest M62-62.0.3192.0.

1) Bad Build on M62-62.0.3181.0 (behaves like on M61 build)
   Good Build on M62-62.0.3182.0 (Issue is not present, progress bar appears on touch) 
   Note: A black screen appears for few seconds on navigating through progress bar
2) Please find logs and video taken on Moto G4 Plus(athene_f)/ 7.0.0 on good build of M62 @ http://go/chrome-androidlogs1/6/746147-m62.
3) On "Opera" browser video pauses for few seconds instead of blank screen on navigating through progress bar.
4) On "firefox" browser video doesn't entering into fullscreen mode at all.

Dear Chrome team, kindly pinging.

+dalecurtis@ in case it rings any bell.

I've tried this again and this is my results:
- Chrome Stable: when I seek, the video slows down dramatically and I can't get the controls back on screen;
- Chrome Beta: when I scrub, the screens goes white and I can't get the controls back;
- Chrome Canary: works fine (it is a version newer than the good build from #12 so it is expected)

Because of the other problems, I'm not sure if the controls not showing is a symptom of the issue or the real issue.

here are some things i found:

- beta is using a video overlay (CVV).
- white background: this is the LayerTreeHost default background color.  what's weird is that using a CVV is supposed to set this to black and also cause it not to be drawn at all.
-- what's really, really weird is that the front buffer of the SV isn't visible during the seek.  where did it go?  see below.
- turning off video overlays causes the gutter => black (expected, no overlay video mode), but seeking works fine again.
- @ToT, it uses a video surface (not CVV), but seeking works fine.
- stable's "slow playback" issue is unrelated to any of this.  when i turn off overlays there, it still takes forever to seek.  though, i don't get slow playback anymore, but i don't get a video either.  only in fs though.

the lack of a visible front buffer @ beta with overlay during seek is extremely weird.  'dumpsys SurfaceFlinger' does show that the overlay is present, and has a front buffer.  since we're supposed to be in overlay video mode, there's not supposed to be a way that the overlay is not visible under the CompositorView; blink is transparent and the the LTH should be not drawing a background.

clearly, that's not happening.  the LTH is drawing a background, and it's the non-overlay-video-mode white.  i'm not sure how it's in that state.

liberato@, what's the next step here?

i retried this @ToT.  now, most videos work fine.

an example of one that didn't one time: http://m.live.sports.media.daum.net/video/general_golf/364185/364186 .  it does not use an overlay, but the display had several badly sized copies of the video.  it reminds me of a bug drawing the gutter, so likely it's not interesting.

i haven't been able to repro it to get a screen shot.

all the other videos i've tried have worked fine @ToT.  i'll try to find one that uses an overlay.

ah -- it didn't use overlays because i wasn't using the right decoder.  i had the new, unfinished MediaCodecVideoDecoder enabled.

after switching back to AVDA, it does use overlays properly on my N5X.  this is different behavior than i saw in c#16, where things were definitely not working at all.  maybe it was just unrelated badness in ToT?

i'll close this as WAI.  please reopen if this still is a problem