Gervase Markham schrieb:
They estimate the increase in download size for a browser shipping Ogg +
Theora-ng + Vorbis at 130k.
Actually I took the liberty of trying to squeeze a functional set of Ogg
decoding libraries into a small footprint (mainly by stripping binaries
and using -Os instead of
Elliotte Harold schrieb:
If we add a video element, should we for the same reasons add an audio
element? If not, why not?
I'd say that audio and video actually are pretty similiar. They need
controls to start playback, to stop playback, to seek, to pause, ...
Perhaps there shouldn't be a video
Also sprach Elliotte Harold:
If we add a video element, should we for the same reasons add an audio
element?
Yes.
It seems to me these two cases are similar enough to justify similar
treatment. Is there any distinction between the two that would suggest
audio is inappropriate while
Cheers Matthew - That's probably the most sensible explanation possible.
Well done. I'm convinced.
Matthew Raymond wrote:
carmen wrote:
On Fri Mar 02, 2007 at 08:09:10PM +0100, David Håsäther wrote:
I don't see the href attribute specified anywhere but the a
element in the current
Consider this example of the output element from the spec:
form
p
input name=a type=number step=any value=0 *
input name=b type=number step=any value=0 =
output name=result onforminput=value = a.value * b.value0/output
/p
/form
This is probably an obvious question, but is the language
On Mon, 05 Mar 2007 22:07:03 +0100, Keryx Web [EMAIL PROTECTED] wrote:
It may be that I've implemented this in the wrong way - corrections are
welcome - but it seems to me that even though xml:base is legal today,
it is **not** supported by UAs. Which makes Anne's proposal, that base
should
On Mar 4, 2007, at 16:31, Geoffrey Sneddon wrote:
Also note that patents haven't stopped the web in the past (see: GIF).
The fact that the Welch patent did not totally wreck the Web and did
not cause browsers to drop GIF support should *not* be considered
evidence of the harmlessness of
On 5 Mar 2007, at 21:07, Keryx Web wrote:
Geoffrey Sneddon wrote:
XHTML 1.0/1.1 doesn't allow xml:base, though, so base is the
only way to set a base URL within the document.
In what way would the XHTML 1.0/1.1 spec **disallow** the use of
this element from the xml namespace? It's not
Has there been any extensive discussion of the article element in Web
Apps 1.0? It is currently described as:
represents a section of a page that consists of a composition that
forms an independent part of a document, page, or site. This could be a
forum post, a magazine or newspaper article,
Hi Simon,
If you load a file from disk, then use any meta information the OS can
provide. (I think Linux can store Content-Type information for files.)
If the OS relies on file extensions (like Windows does) then use that.
Some Linux file systems might potentially be capable of storing extra
On Tue, 06 Mar 2007 02:56:31 +1100, Maik Merten [EMAIL PROTECTED] wrote:
Elliotte Harold schrieb:
If we add a video element, should we for the same reasons add an audio
element? If not, why not?
I'd say that audio and video actually are pretty similiar. They need
controls to start playback,
Elliotte Harold wrote:
Has there been any extensive discussion of the article element in Web
Apps 1.0? It is currently described as:
represents a section of a page that consists of a composition that
forms an independent part of a document, page, or site. This could be a
forum post, a
Leons Petrazickis wrote:
The sister issue of easy-of-typing is ease-of-reading. Human editing
of raw HTML isn't going away. In headier coding disciplines, high
readability is prized. Most code -- even HTML code -- will spend a lot
more of its time being maintained than being written. Being
The HyperTextuality Firefox extension I've been writing attempts to work
out the most relevant URI for a given piece of content, for bookmarking
or quoting. Front pages of blogs, the most important use-case, also pose
a particular problem as many blogs don't have an obvious structure (to
an
Maciej Stachowiak wrote:
Restricting the types of content that the video element can handle
will stifle future innovation, and will likely be ignored by browser
vendors who decide they would like to support new formats. It would
also be unprecedented relative to type restrictions on
15 matches
Mail list logo
