Fix SplitRange() logic in SourceBufferRange to transfer next buffer position appropriately

Fix SplitRange() logic in SourceBufferRange to transfer next buffer position appropriately

Adds logic to transfer the waiting-for-next-keyframe state to the split range
if necessary.

BUG=NONE
TEST=media_unittests


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=146274

[vrk (LEFT CHROMIUM), 2012-07-10 19:56:33]

Hey Aaron, as I was writing SourceBufferRange::ResetNextBufferPosition() in CL
10766021, I realized I handled this edge case incorrectly.

[acolwell GONE FROM CHROMIUM, 2012-07-10 20:19:32]

LGTM

https://chromiumcodereview.appspot.com/10703125/diff/1/media/filters/source_b...
File media/filters/source_buffer_stream.cc (right):

https://chromiumcodereview.appspot.com/10703125/diff/1/media/filters/source_b...
media/filters/source_buffer_stream.cc:828: split_range->next_buffer_index_ =
next_buffer_index_ - keyframe_index;
DCHECK(!waiting_for_keyframe_) ?

[vrk (LEFT CHROMIUM), 2012-07-10 20:34:54]

https://chromiumcodereview.appspot.com/10703125/diff/1/media/filters/source_b...
File media/filters/source_buffer_stream.cc (right):

https://chromiumcodereview.appspot.com/10703125/diff/1/media/filters/source_b...
media/filters/source_buffer_stream.cc:828: split_range->next_buffer_index_ =
next_buffer_index_ - keyframe_index;
On 2012/07/10 20:19:32, acolwell wrote:
> DCHECK(!waiting_for_keyframe_) ?

Done.

[commit-bot: I haz the power, 2012-07-10 22:15:42]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/vrk@chromium.org/10703125/4001

[commit-bot: I haz the power, 2012-07-12 01:36:53]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/vrk@chromium.org/10703125/8002

[commit-bot: I haz the power, 2012-07-12 02:38:08]

Change committed as 146274