- From: Ami Fischman <fischman@google.com>
- Date: Thu, 12 Dec 2013 13:12:06 -0800
- To: Simon Pieters <simonp@opera.com>
- Cc: Harald Alvestrand <harald@alvestrand.no>, public-webrtc@w3.org
Received on Thursday, 12 December 2013 21:12:37 UTC
Assuming the OP runs javascript inside a browser and not inside a specification, 328140<https://code.google.com/p/chromium/issues/detail?id=328140>still needs to get done :) -a On Thu, Dec 12, 2013 at 1:07 PM, Simon Pieters <simonp@opera.com> wrote: > On Wed, 11 Dec 2013 20:28:35 +0100, Ami Fischman <fischman@google.com> > wrote: > > >>> The <video> tag seems to have no event handlers >>> >> >> >> ? >> http://www.whatwg.org/specs/web-apps/current-work/ >> multipage/the-video-element.html#mediaeventslists >> many events that fire on <video>. >> The typical answer for getting initial resolution is to listen for first >> timeupdate event and then query the <video>'s video{Width,Height}. >> >> >> Perhaps one should ask for a "videochange" event? >>> >>> >> Yes, please :) >> > > Prayer answered: http://html5.org/r/8347 > > cheers > > > That would be useful for static/VOD (not webrtc/gUM-related) >> mid-stream-resolution-changing videos, as well as MSE, too. >> >> Cheers, >> -a >> > > > -- > Simon Pieters > Opera Software >
Received on Thursday, 12 December 2013 21:12:37 UTC