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

Issue 303403002: Eliminate MediaPlayer & MediaPlayerClient abstractions(ground work for eliminating rate APIs) (Closed)

Created:
6 years, 6 months ago by Srirama
Modified:
6 years, 6 months ago
CC:
chromium-reviews, fischman+watch_chromium.org, jam, mcasas+watch_chromium.org, feature-media-reviews_chromium.org, darin-cc_chromium.org, wjia+watch_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Visibility:
Public.

Description

Eliminate MediaPlayer & MediaPlayerClient abstractions(ground work for eliminating rate APIs) BUG=350571

Patch Set 1 : Eliminate MediaPlayer & MediaPlayerClient abstractions(ground work for eliminating rate APIs) #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+3 lines, -0 lines) Patch
M content/renderer/media/webmediaplayer_impl.cc View 1 chunk +3 lines, -0 lines 1 comment Download

Messages

Total messages: 5 (0 generated)
Srirama
This patch is to facilitate removal of rate, setRate APIs from WebMediaPlayerClientImpl. I have moved ...
6 years, 6 months ago (2014-05-30 12:25:56 UTC) #1
acolwell GONE FROM CHROMIUM
https://codereview.chromium.org/303403002/diff/20001/content/renderer/media/webmediaplayer_impl.cc File content/renderer/media/webmediaplayer_impl.cc (right): https://codereview.chromium.org/303403002/diff/20001/content/renderer/media/webmediaplayer_impl.cc#newcode405 content/renderer/media/webmediaplayer_impl.cc:405: if (rate == playback_rate_) Do we really need this? ...
6 years, 6 months ago (2014-06-02 22:37:02 UTC) #2
Srirama
On 2014/06/02 22:37:02, acolwell wrote: > https://codereview.chromium.org/303403002/diff/20001/content/renderer/media/webmediaplayer_impl.cc > File content/renderer/media/webmediaplayer_impl.cc (right): > > https://codereview.chromium.org/303403002/diff/20001/content/renderer/media/webmediaplayer_impl.cc#newcode405 > ...
6 years, 6 months ago (2014-06-03 11:10:21 UTC) #3
acolwell GONE FROM CHROMIUM
On 2014/06/03 11:10:21, Srirama wrote: > On 2014/06/02 22:37:02, acolwell wrote: > > > https://codereview.chromium.org/303403002/diff/20001/content/renderer/media/webmediaplayer_impl.cc ...
6 years, 6 months ago (2014-06-03 16:32:53 UTC) #4
Srirama
6 years, 6 months ago (2014-06-03 17:08:47 UTC) #5
On 2014/06/03 16:32:53, acolwell wrote:
> On 2014/06/03 11:10:21, Srirama wrote:
> > On 2014/06/02 22:37:02, acolwell wrote:
> > >
> >
>
https://codereview.chromium.org/303403002/diff/20001/content/renderer/media/w...
> > > File content/renderer/media/webmediaplayer_impl.cc (right):
> > > 
> > >
> >
>
https://codereview.chromium.org/303403002/diff/20001/content/renderer/media/w...
> > > content/renderer/media/webmediaplayer_impl.cc:405: if (rate ==
> playback_rate_)
> > > Do we really need this? Shouldn't the caller in Blink simply not make the
> call
> > > to setRate() if rate is identical?
> > 
> > I just thought instead of querying webmediaplayer_impl for rate value and
> > compare before calling setRate, if we move the condition to
> webmediaplayer_impl
> > we need not have two function calls.
> > If this is not required i will add the conditions at the blink side itself.
> > Please suggest.
> 
> But this would mean that all WebMediaPlayer implementations would have to have
> this same logic. The WebMediaPlayer should always just mirror what
> HTMLMediaElement set last. You shouldn't have to query WebMediaPlayer for its
> last value. HTMLMediaElement should always know what the last rate it set was
> because it was the one that set it last.

Thanks for the explanation. I got it now.

Powered by Google App Engine
This is Rietveld 408576698