- From: poot <cvsmail@w3.org>
- Date: Wed, 27 Apr 2011 18:14:36 -0400
- To: public-html-diffs@w3.org
hixie: mention the problem with UAs that don't support playbackRate reliably. (whatwg r6033) http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4844&r2=1.4845&f=h http://html5.org/tools/web-apps-tracker?from=6032&to=6033 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.4844 retrieving revision 1.4845 diff -u -d -r1.4844 -r1.4845 --- Overview.html 27 Apr 2011 05:08:19 -0000 1.4844 +++ Overview.html 27 Apr 2011 22:11:01 -0000 1.4845 @@ -26753,7 +26753,9 @@ allowing it to be garbage collected, or, even better, by removing the element's <code title="attr-media-src"><a href="#attr-media-src">src</a></code> attribute and any <code><a href="#the-source-element">source</a></code> element descendants, and invoking the - element's <code title="dom-media-load"><a href="#dom-media-load">load()</a></code> method.<div class="impl"> + element's <code title="dom-media-load"><a href="#dom-media-load">load()</a></code> method.<p>Similarly, when the playback rate is not exactly 1.0, hardware, + software, or format limitations can cause video frames to be dropped + and audio to be choppy or muted.<div class="impl"> <h5 id="best-practices-for-implementors-of-media-elements"><span class="secno">4.8.10.18 </span>Best practices for implementors of media elements</h5>
Received on Wednesday, 27 April 2011 22:14:38 UTC