- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 30 Mar 2011 00:14:22 +0000 (UTC)
- To: Frank Olivier <Frank.Olivier@microsoft.com>
- cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Paul Cotton <Paul.Cotton@microsoft.com>, "HTML WG (public-html@w3.org)" <public-html@w3.org>
On Tue, 29 Mar 2011, Frank Olivier wrote: > > I'd prefer that we still change the spec as proposed in the original > ISSUE-147 Change Proposal [1] to make it clear that the user agent might > not support the requested rate. Therefore I am not currently willing to > withdraw that Change Proposal for ISSUE-147. Yesterday you said "my preference based on the recent discussions would be for a change that keeps the (settable) playbackrate attribute (for compatibility with any existing pages)" which seems to contradict your change proposal. I'm confused. Could you clarify how your change proposal is intended to work in the cases Philip raised, where the user agent doesn't know in advance what playback rates it can support? Also, how is it intended to work with multiple controllers? It seems the proposal would break any controller that relied on playbackRate to determine whether the user was fast-forwarding or not. > I do agree that adding a metric object should be a separate Last Call > issue. Is someone going to file a separate bug for this requirement? Adding metrics is on the list of features to add to <video> in the spec (search the source for "feedback to the script on how well the video is playing"). -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 30 March 2011 00:14:52 UTC