Hi Chris,
I provide an additional comparison at
http://people.xiph.org/~maikmerten/youtube/ using different content.
This doesn't qualify as "more movement/action" (it's hard to get free HD
samples of such content in good quality), but content like the one I
used is common nonetheless on community
On Tue, 16 Jun 2009 11:51:05 +0100, Aryeh Gregor
wrote:
is a very poor solution, and would be too. You
should use graceful degradation/progressive enhancement instead (in
both cases).
Graceful degradation is not necessarily possible with JavaScript. For
instance, consider a real-time
On Jun 15, 2009, at 4:19 PM, Kristof Zelechovski wrote:
The complexity of using a set implemented as hash table is quadratic
in the
number of elements because of hash collisions.
Removing duplicates from a list of length N using an auxiliary set is
average-case O(N) because insertion and
Media queries can be done the same way as for images. Similarly, the server
can choose to serve a localized version of any resource whatsoever. These
customizations should not be put into VIDEO because their scope is wider.
IMHO,
Chris
I think it would be useful to add "fullscreenable" (or more refined name)
attribute to arbitrary element, so users could be able to full-screen
DOM subtrees, that document author marked as "fullscreenable".
Usage: User choses area that he wants to fullscreen, peforms UA-specific
action there("go t
At 18:12 +0200 16/06/09, Kristof Zelechovski wrote:
The first video source that can be played wins. You cannot provide
alternative versions for different languages or resolutions in one VIDEO
element.
Chris
but there are media queries, and I have posted a couple of times that
we should consi
Kristof Zelechovski wrote:
> The first video source that can be played wins. You cannot provide
> alternative versions for different languages or resolutions in one VIDEO
> element.
If the browser decides that a video is too high resolution and cannot be
played on this system, then why can't it f
The first video source that can be played wins. You cannot provide
alternative versions for different languages or resolutions in one VIDEO
element.
Chris
Am Montag, den 15.06.2009, 13:26 -0700 schrieb Thomas Powell:
> 2) Body Usage
>
>
>
> Warning: Styles required for correct rendering
>
HTML is first, and foremost, a semantic language. Why should
presentational information affect the semantics ?
Also, several further questions:
* How
On Mon, Jun 15, 2009 at 7:23 PM, Kornel Lesinski wrote:
> is a very poor solution, and would be too. You should
> use graceful degradation/progressive enhancement instead (in both cases).
Graceful degradation is not necessarily possible with JavaScript. For
instance, consider a real-time game w
On Mon, 15 Jun 2009 23:45:02 +0200, Boris Zbarsky wrote:
> Anne van Kesteren wrote:
>> On Mon, 15 Jun 2009 18:25:03 +0200, Adam Roben wrote:
>>> DOM 3 Core defines the DOMStringList interface [1], [...]
>> I don't think anybody actually implements this interface though or is
>> planning to.
>
On Tue, Jun 16, 2009 at 1:37 AM, Stephen Paul Weber wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Two questions.
>
> 1) What is the difference between and in the spec? The
> wording is quite different, but seem to say basically the same thing: "plugin
> data".
is not necessari
12 matches
Mail list logo
