Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(318)

Issue 10342005: media::SeekableBuffer should use kNoTimestamp() instead of zero. (Closed)

Created:
8 years, 7 months ago by scherkus (not reviewing)
Modified:
8 years, 7 months ago
CC:
chromium-reviews, feature-media-reviews_chromium.org
Visibility:
Public.

Description

media::SeekableBuffer should use kNoTimestamp() instead of zero. I noticed this while debugging bug 120396 that the reported time remained zero even after appending the initial audio buffer that has a timestamp of zero. BUG=none TEST=none Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=135050

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+22 lines, -14 lines) Patch
M media/base/seekable_buffer.cc View 2 chunks +2 lines, -3 lines 0 comments Download
M media/base/seekable_buffer_unittest.cc View 2 chunks +20 lines, -11 lines 1 comment Download

Messages

Total messages: 2 (0 generated)
scherkus (not reviewing)
8 years, 7 months ago (2012-05-02 21:30:39 UTC) #1
vrk (LEFT CHROMIUM)
8 years, 7 months ago (2012-05-02 22:18:06 UTC) #2
LGTM

https://chromiumcodereview.appspot.com/10342005/diff/1/media/base/seekable_bu...
File media/base/seekable_buffer_unittest.cc (right):

https://chromiumcodereview.appspot.com/10342005/diff/1/media/base/seekable_bu...
media/base/seekable_buffer_unittest.cc:331:
EXPECT_EQ(kNoTimestamp().ToInternalValue(),
nit: change to kNoTS?

Powered by Google App Engine
This is Rietveld 408576698