On 2011-04-08 23:20, Jukka K. Korpela wrote:
Tab Atkins Jr. wrote:
On Fri, Apr 8, 2011 at 12:30 PM, Jukka K. Korpela
jkorp...@cs.tut.fi wrote:
Tab Atkins Jr. wrote:
details is definitely something we want to make fully
author-stylable.
I don’t. Who’s this ”we” you are talking about, and
Ah, thanks for the link. I've included Silverlight stats, too, for
completeness. If somebody knows about QuickTime stats, that would be
another good one to add, I guess.
Cheers,
Silvia.
On Fri, Apr 8, 2011 at 5:21 PM, Jeroen Wijering
jer...@longtailvideo.com wrote:
On Apr 7, 2011, at 8:11 AM,
Lachlan Hunt wrote:
We would like our
implementations to be compatible as far as author styling is
concerned, and so it is very useful to discuss the fine-tuning of CSS
styling before we ship. If we did not do this, then you and every
other author would most certainly complain when Opera and
Sorry for the top posting, but I would like to reiterate my considered
opinion that Speex be supported for recording. It is the standard
format available from Adobe Flash recording, low bandwidth, open
source and unencumbered, efficient, and it is high quality for its
bandwidth.
On Tue, Mar 29,
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-July/027455.html
A big +1 to the proposal in this thread, to allow specifying
Content-Disposition behavior in anchors. a download=filename.txt would
have the effect of adding (or overriding) the header Content-Disposition:
attachment;
I'm working on DOM-based editing tools in my spare time, and have been for
several years. I use DOM mutation events to build transactions - objects
which let me undo DOM mutations and redo them.
There's a strong suggestion that DOM mutation observers should replace DOM
mutation events
getContext doesn't specify error handling. WebGL solves this oddly: if an
error occurs, it dispatches an event with error details at the canvas. It's
odd for a synchronous API to report error information with an event; it
would make a lot more sense to raise an exception. However, getContext
