RESOLVED FIXED 129926
Add Remote Control command support to HTMLMediaElement
https://bugs.webkit.org/show_bug.cgi?id=129926
Summary Add Remote Control command support to HTMLMediaElement
Jer Noble
Reported 2014-03-07 14:59:46 PST
Add Remote Control command support to HTLMediaElement
Attachments
Patch (13.18 KB, patch)
2014-03-07 15:04 PST, Jer Noble
eric.carlson: review+
Jer Noble
Comment 1 2014-03-07 15:04:55 PST
Eric Carlson
Comment 2 2014-03-13 14:37:47 PDT
Comment on attachment 226172 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=226172&action=review > Source/WebCore/html/HTMLMediaElement.cpp:3059 > + } else > + setPlaybackRate(nextScanRate()); > +} Do we really want to increase the scan rate to infinity (and beyond)? > Source/WebCore/html/HTMLMediaElement.cpp:5937 > + { } // Do nothing Nit: I don't think "{ }" is necessary, won't a semi-colon work?
Jer Noble
Comment 3 2014-03-13 14:47:07 PDT
(In reply to comment #2) > (From update of attachment 226172 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=226172&action=review > > > Source/WebCore/html/HTMLMediaElement.cpp:3059 > > + } else > > + setPlaybackRate(nextScanRate()); > > +} > > Do we really want to increase the scan rate to infinity (and beyond)? We'll max out at ScanMaximumRate (8x) inside of nextScanRate(). > > Source/WebCore/html/HTMLMediaElement.cpp:5937 > > + { } // Do nothing > > Nit: I don't think "{ }" is necessary, won't a semi-colon work? Clang++ complains about only a semicolon, and explicitly suggests "{ }" for an empty statement.
Eric Carlson
Comment 4 2014-03-13 16:08:33 PDT
Comment on attachment 226172 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=226172&action=review >>> Source/WebCore/html/HTMLMediaElement.cpp:3059 >>> +} >> >> Do we really want to increase the scan rate to infinity (and beyond)? > > We'll max out at ScanMaximumRate (8x) inside of nextScanRate(). Oops, I looked right past that!
Jer Noble
Comment 5 2014-03-14 10:23:07 PDT
Note You need to log in before you can comment on or make changes to this bug.