Ian Hickson wrote:
On Fri, 14 Nov 2008, Shannon wrote:
I don't see any value in the user-agent specified amount of time delay
in stopping scripts. How can you write cleanup code when you have no
consistency in how long it gets to run (or if it runs at all)?
The user-agent
While I don't strongly object to the suggestion as such, there are 2
things I want to point out.
1. It is not clear (to me at least) what balance means for anything by
mono/stereo audio. What is the expected behaviour for 5.1 audio?
2. Balance is just one kind of audio filter effect. The more
On Tue, 28 Oct 2008, Charles Iliya Krempeaux wrote:
I was looking over the spec and looking to see how I'd go about creating
a custom progress bar. (Like you see as part of scrub bars.)
To do this I'd imagine that a playing video would have to send out
events fast enough so that the
On Sat, 1 Nov 2008, Chris Double wrote:
Some video formats don't make it easy to get the duration.
Indeed.
For example, Ogg files can be concatenated to form a single playable
file. To compute the duration you need to do multiple seeks to find the
chains and total the durations of each
On Thu, 6 Nov 2008, Philip J�genstedt wrote:
More random issues related to HTMLMediaElement
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#dom-media-buffered
The buffered attribute must return a static normalized TimeRanges
object
The phrasing for the other
On Tue, 11 Nov 2008, Robert O'Callahan wrote:
Should video and audio elements be able to load and play resources
from other origins? [...]
Reasons to disallow cross-origin playback are a little less obvious. The
main issue is the need to avoid leaking information from, say,
On Wed, 12 Nov 2008, Biju [EMAIL PROTECTED] wrote:
I see a problem while using video_element.currentTime instead of
video_element.start
ie, recent firefox nightly build removed video_element.start before that
we could do following to make a movie with new URL start from 10th
second
On Fri, 14 Nov 2008, Silvia Pfeiffer wrote:
On a little bit of a side not, may I point out that there is an updated
RFC for Ogg media types at http://www.ietf.org/rfc/rfc5334.txt and it
explicitly includes the codecs parameter with standard values for the
current ones supported by Ogg.
On Sat, 15 Nov 2008, Philip J�genstedt wrote:
The changes look like improvements to me, but I have some questions.
1. Is there any particular reason why step 7 generate the list of
potential media resources is done in the synchronous part of the
algorithm? Would it for example be an error
On Thu, 13 Nov 2008, Pierre-Olivier Latour wrote:
And the suggested hack is not even really usable: if you have a video coming
from a NTSC DV source as 720x480 improperly transcoded to say MP4 720x480
square pixels, using the theoretical 10:11 pixel aspect ratio will _not_ make
it look
[Skip forward to paragraph four to avoid the historical backdrop. ]
1. Seven or eight years ago I was working on a mini-app [1] in the browser
using VML. It allowed folks to build graphs on-screen with a GUI and then to do
standard graph theoretic things: color nodes, find shortest paths, find
Ian Hickson wrote:
Video and audio playback is already extremely CPU intensive, we
shouldn't require the UA to burn extra cycles doing unnecessary work.
I agree. That was exactly the thinking behind the timeupdate event. It
allows the UA to determine how fast to update the UI without hurting
On Sun, 16 Nov 2008, Jonas Sicking wrote:
I think one problem is that a timer can be set to fire much less often
than the current time changes.
For example the UI doesn't need to be updated more than maybe twice a
second for most videos (since it won't move more than one pixel in that
On Mon, Nov 17, 2008 at 3:19 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
Ian Hickson wrote:
Video and audio playback is already extremely CPU intensive, we shouldn't
require the UA to burn extra cycles doing unnecessary work.
I agree. That was exactly the thinking behind the timeupdate
Maybe it is possible to combine the two approaches 2) and 3) as
proposed by Robert O'Callahan.
The Access-Control-Allow-Origin: * header would then allow access
to more information than is available through the restricted API.
(This was an approach suggested on #theora).
Regards,
Silvia.
On
On Mon, 17 Nov 2008, Silvia Pfeiffer wrote:
Maybe it is possible to combine the two approaches 2) and 3) as
proposed by Robert O'Callahan.
The Access-Control-Allow-Origin: * header would then allow access
to more information than is available through the restricted API.
(This was an
On Mon, Nov 17, 2008 at 12:46 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Wed, 12 Nov 2008, Biju [EMAIL PROTECTED] wrote:
On Fri, 14 Nov 2008, Silvia Pfeiffer wrote:
I still feel rather dubious about the currentTime attribute of the video
element.
When it is used to tell a server about
On Mon, Nov 17, 2008 at 12:49 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Fri, 14 Nov 2008, Silvia Pfeiffer wrote:
On a little bit of a side not, may I point out that there is an updated
RFC for Ogg media types at http://www.ietf.org/rfc/rfc5334.txt and it
explicitly includes the codecs
18 matches
Mail list logo
