MSE: Relocate IncreaseDurationCB to LegacyFrameProcessor
commit2595696c35ee7e805199eb3009d85ec5475f65b7
authorwolenetz@chromium.org <wolenetz@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 18 Mar 2014 18:46:29 +0000 (18 18:46 +0000)
committerwolenetz@chromium.org <wolenetz@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 18 Mar 2014 18:46:29 +0000 (18 18:46 +0000)
treeba35d45f0558fdc1f96d7e293e034c89f311e875
parente480e169e72bceecef04fe63c3bfea1f201af3bd
MSE: Relocate IncreaseDurationCB to LegacyFrameProcessor

Upcoming compliant FrameProcessor implementation will rely on
caller to update the duration to be more coherent with
HTMLMediaElement.buffered upon completing frame processing. Only the
LegacyFrameProcessor will use IncreaseDurationCB, so this change
pushes that callback purely into the legacy code.

R=acolwell@chromium.org
BUG=249422
TEST=All media_unittests and http/tests/media layout tests pass locally on Linux.

Review URL: https://codereview.chromium.org/202583002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@257701 0039d316-1c4b-4281-b951-d872f2087c98
media/filters/frame_processor_base.cc
media/filters/frame_processor_base.h
media/filters/legacy_frame_processor.cc
media/filters/legacy_frame_processor.h