Re: [whatwg] VIDEO and pitchAdjustment

6 at 1:09 PM, Garrett Smith <dhtmlkitc...@gmail.com> > wrote: > > On Wed, Mar 2, 2016 at 2:36 AM, Philip Jägenstedt <phil...@opera.com> > wrote: > >> On Wed, Mar 2, 2016 at 5:08 PM, Paul Adenot <pade...@mozilla.com> > wrote: > >>> > >

Re: [whatwg] VIDEO and pitchAdjustment

Gecko uses code that can do arbitrary pitch adjustment, unrelated to time-stretching (which is speed change with pitch compensation). Paul. On Wed, Mar 2, 2016 at 5:00 AM, Philip Jägenstedt wrote: > On Wed, Mar 2, 2016 at 9:19 AM, Garrett Smith >

[whatwg] source media attribute behavior, static or dynamic ?

Currently implementing the media attribute of the source element in Gecko, we are unsure about what the specification requires us to do there. Considering this example : video source src=lowres.webm media=max-width:500px source src=highres.webm /video what is the expected behavior of a

Re: [whatwg] source media attribute behavior, static or dynamic ?

As far as I can tell, the behaviour here is strictly and unambiguously defined, leaving only one possible interpretation, so it's not clear to me how to make it less ambiguous. Could you elaborate on what interpretations of the spec you think are possible? We have two possible

[whatwg] media attribute of source element, default behavior on getting the property.

Currently implementing the media attribute for the source element in Gecko, we are not sure on how to interpret the spec when the attribute is not set in the HTML source. Considering this snipped of code : video source id=asource src=media.webm /video What should

[whatwg] [media] played member expected behavior.

The played member [1] description of the media element states : The played attribute must return a new static normalized TimeRanges object that represents the ranges of the media resource, if any, that the user agent has so far rendered, at the time the attribute is evaluated. Currently