I'm currently creating a custom HTML video player UI. What I'm trying to
achieve is a seek bar control—a horizontal slider that allows the user to
seek to a specific point in time. Right now the basic functionality of this
can be achieved using a range input with a max value set to the video's
On Fri, 13 Jan 2012 01:53:23 +0100, Aryeh Gregor a...@aryeh.name wrote:
On Thu, Jan 12, 2012 at 12:46 PM, Francis Boumphrey
boumphre...@gmail.com wrote:
e.g. video src='myvideo.mp4' controls
and my user agent does not support the format, all I get (in my
versions of
Opera and Firefox) is a
On 1/13/12 2:50 AM, Roman Rudenko wrote:
True. In its current form, beforeload is not very useful for partial processing.
What if we had 'beforedownload' event specifically for resource
fetching, and constructed stub elements to feed it as event.target
when load is readahead-induced?
That
On Sat, 25 Jun 2011, David W. Kingori wrote:
My name is David Kingori and I am absolutely fascinated by the
capabilities of HTML5. I was wondering if you could enlighten me on how
I could convert a Microsoft Word document of mine into an HTML5 page?
There are various Word - to - HTML
On Tue, 28 Jun 2011, Anne van Kesteren wrote:
Is there a way we can make these consistent somehow? Maybe move
document.documentURI to Web Applications 1.0? With createHTMLDocument() I get
these results:
document.URL document.documentURI
Gecko about:blankabout:blank
Dear WHAT WG,
The CSS WG published a Last Call Working Draft of the CSS3 Image Values and
Replaced Content module:
http://www.w3.org/TR/2012/WD-css3-images-20120112/
We believe there is some overlap of interest with HTML, and therefore we'd
appreciate your review of the features therein,
On Thu, 15 Dec 2011, Boris Zbarsky wrote [edited for context]:
On 12/15/11 3:10 PM, Ian Hickson wrote [edited for context]:
I might be open to changing the current spec text -- presumably to
just define wbr as follows, or something similar (though using
U+200B would probably affect text
Hi whatwg,
I'd like to draw non-antialiased lines in a canvas. Currently it seems
that the only way to do this is to directly access the pixel data.
Is there a reason there's no way to turn off antialiasing?
Possible API:
context.antialias = false