[whatwg] Reporting mid-stream resolution change on

Today the 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, which is

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

by http://www.whatwg.org/specs/web-apps/current-work/#event-media-resize's Preconditions. Would it make sense to make resize fire right before metadataloaded fires and remove its Preconditions (both mimicking durationchange)? Cheers, -a On Thu, Dec 12, 2013 at 12:04 PM, Ian Hickson wrote

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

On Thu, Dec 12, 2013 at 2:56 PM, Ian Hickson 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 elements to f

[whatwg] Media sink device selection on /

Recently 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

Re: [whatwg] Media sink device selection on /

On Wed, Dec 18, 2013 at 8:38 PM, Ian Hickson wrote: > On Tue, 17 Dec 2013, Ami Fischman wrote: > > 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): &

Re: [whatwg] Media sink device selection on /

On Sun, Jan 12, 2014 at 8:47 PM, Philip Jägenstedt wrote: [...] > 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 > going to actuall

Re: [whatwg] Media sink device selection on /

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 wrote: > On Tue, Jan 14, 2014 at 5:51 AM, Ami Fischman > wrote: > > On Sun, Jan 12

Re: [whatwg] Media sink device selection on /

s editor's 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 wrote: > On Wed, 18 Dec 2013, Ami Fischman wrote: > > On Wed, Dec 18, 2013

Re: [whatwg] Media sink device selection on /

Ian, On Fri, Feb 7, 2014 at 4:55 PM, Ian Hickson 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: http://dev.w3.org/2011/webrtc/editor/getusermedia.html Chee

Re: [whatwg] Media sink device selection on /

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 wrote: > On Mon, 3 Mar 2014, Ami Fischman wrote: > > > > Looks lik

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

On Thu, Jan 12, 2012 at 9:46 AM, Francis Boumphrey wrote: > 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 to follow the spec.