Re: [whatwg] Media sink device selection on audio/video

2014-04-07 Thread Ami Fischman
Thanks Ian. I pinged public-media-capture about this and https://www.w3.org/Bugs/Public/show_bug.cgi?id=25245 is now tracking making that spec better specified. On Wed, Apr 2, 2014 at 10:52 AM, Ian Hickson i...@hixie.ch wrote: On Mon, 3 Mar 2014, Ami Fischman wrote: Looks like we're back

Re: [whatwg] Media sink device selection on audio/video

2014-03-03 Thread Ami Fischman
Ian, On Fri, Feb 7, 2014 at 4:55 PM, Ian Hickson i...@hixie.ch wrote: Can you let us know when there's a URL that will permanently hold the latest (including day-to-day updates) spec? Looks like we're back in business: Latest editor's draft:

Re: [whatwg] Media sink device selection on audio/video

2014-02-07 Thread Ami Fischman
draft ( http://dev.w3.org/2011/webrtc/editor/archives/20131225/getusermedia.html) for the pieces of the spec discussed in this thread here. Cheers, -a On Fri, Feb 7, 2014 at 2:28 PM, Ian Hickson i...@hixie.ch wrote: On Wed, 18 Dec 2013, Ami Fischman wrote: On Wed, Dec 18, 2013 at 8:38 PM, Ian

Re: [whatwg] Media sink device selection on audio/video

2014-01-13 Thread Ami Fischman
On Sun, Jan 12, 2014 at 8:47 PM, Philip Jägenstedt phil...@opera.comwrote: [...] Do you mean to make this per-origin as well? (It will require storing that information per-origin forever, or until some invisible timeout.) That seems about as restrictive as one could make it, but is the API

Re: [whatwg] Media sink device selection on audio/video

2014-01-13 Thread Ami Fischman
Hmm; I wasn't thinking in terms of per-device, only per-origin and per-browser/machine. Seems like a conversation for public-media-capture? On Mon, Jan 13, 2014 at 3:30 PM, Philip Jägenstedt phil...@opera.comwrote: On Tue, Jan 14, 2014 at 5:51 AM, Ami Fischman fisch...@chromium.org wrote

[whatwg] Media sink device selection on audio/video

2013-12-17 Thread Ami Fischman
Recently https://www.w3.org/Bugs/Public/show_bug.cgi?id=23263 Navigator acquired the ability to enumerate media output devices (in addition to input devices): http://dev.w3.org/2011/webrtc/editor/getusermedia.html#enumerating-devices It would be nice to allow media elements to direct their output

[whatwg] Reporting mid-stream resolution change on video

2013-12-12 Thread Ami Fischman
Today the video tag exposes video{Width,Height} attributes that allow the page to discover the resolution of the playing media once metadataloaded has fired. However there is no way for the page to find out that the media resolution has changed mid-stream (short of polling the tag constantly,

Re: [whatwg] Reporting mid-stream resolution change on video

2013-12-12 Thread Ami Fischman
, Ami Fischman wrote: Today the video tag exposes video{Width,Height} attributes that allow the page to discover the resolution of the playing media once metadataloaded has fired. However there is no way for the page to find out that the media resolution has changed mid-stream (short

Re: [whatwg] Reporting mid-stream resolution change on video

2013-12-12 Thread Ami Fischman
On Thu, Dec 12, 2013 at 2:56 PM, Ian Hickson i...@hixie.ch wrote: I suppose we could fire resize on initial load as well. I guess it depends on what code that uses this looks like. Is the initial size change the same kind of code as resizing, or is it different code? (e.g. will one set up

Re: [whatwg] video element not ready for prime time

2012-01-12 Thread Ami Fischman
On Thu, Jan 12, 2012 at 9:46 AM, Francis Boumphrey boumphre...@gmail.comwrote: In which order does the user-agent check the source files (in Chrome it seems to be in the order in which they are written, but there is no guidance here in the spec. The spec does specify this, and chrome fails