diff options
| author | wolenetz@chromium.org <wolenetz@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-06-17 23:42:00 +0000 |
|---|---|---|
| committer | wolenetz@chromium.org <wolenetz@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-06-17 23:42:00 +0000 |
| commit | 818bcf449c3202727190ecc1f398a504f01e8644 (patch) | |
| tree | 417e6ab4a226b380ab0cb08dd29f833a991154ea /content/browser/android/surface_texture_peer_browser_impl.h | |
| parent | 1e015df3e06182cc7b4391a30bd4ca252d67d5a5 (diff) | |
| download | chromium_src-818bcf449c3202727190ecc1f398a504f01e8644.zip chromium_src-818bcf449c3202727190ecc1f398a504f01e8644.tar.gz chromium_src-818bcf449c3202727190ecc1f398a504f01e8644.tar.bz2 | |
MSE: Allow negative parsed frame PTS/DTS in FrameProcessor
r274473 did not remove sanity checks for negative PTS/DTS that occur
prior to any adjustment based on timestampOffset. Current MSE spec does
not call for issuing decode error if PTS or DTS are negative at the top
of the coded frame processing loop. This change removes the sanity
checks that are not spec-compliant.
R=acolwell@chromium.org
BUG=381114
TEST=FrameProcessorTest.AllowNegativeFramePTSAndDTSBeforeOffsetAdjustment
Review URL: https://codereview.chromium.org/334363006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@277903 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser/android/surface_texture_peer_browser_impl.h')
0 files changed, 0 insertions, 0 deletions