| commit | d7625e643c2319744428f9de45ec2703a2023fc0 | [log] [tgz] |
|---|---|---|
| author | philipj@opera.com <philipj@opera.com@bbb929c8-8fbe-4397-9dbb-9b2b20218538> | Wed Mar 05 07:27:14 2014 |
| committer | philipj@opera.com <philipj@opera.com@bbb929c8-8fbe-4397-9dbb-9b2b20218538> | Wed Mar 05 07:27:14 2014 |
| tree | 8666068d178cbe4bb6a63c8e14b2578ce4be0210 | |
| parent | 49a4c3b87dcd75d0446b96963f014a8e0140df37 [diff] |
Count how often a Media Fragments URI is applied in HTMLMediaElement http://lists.w3.org/Archives/Public/public-media-fragment/2014Feb/0000.html http://lists.w3.org/Archives/Public/public-media-fragment/2014Feb/0002.html In this thread about looping over media fragments it became clear that no spec actually says how media fragment end times integrate in HTMLMediaElement. (The start time is mapped to the "initial playback position", which almost matches what Blink does.) Blink/WebKit pauses at the fragment end time once. Firefox Nightly does the same, while IE11 appears to not support MF URIs at all. The counter data will tell us whether or not breaking changes can be made and the relative usage could help inform the spec discussion. BUG=none R=acolwell@chromium.org Review URL: https://codereview.chromium.org/185363002 git-svn-id: svn://svn.chromium.org/blink/trunk@168441 bbb929c8-8fbe-4397-9dbb-9b2b20218538