After a brief correspondence with Robin Berjon he suggested I post this
suggestion here.
After having problems with detecting support for the HTML5 'input' event (
http://goo.gl/XNSg5 http://goo.gl/rAa5f) I started wondering if there was a
DOM specification for detecting support for DOM events in
I would love even a painfully slow implementation provided by the
browser. I have encountered lots of cases where being able to talk a
protocol requires computing a sha1 or an md5 hash. Speed has never
been the problem for me, but external javascript library dependencies
are painful to maintain.
I have updated the editor's draft of the File API (special winter
solstice edition).
In particular:
On 12/20/10 8:32 PM, Michael Nordman wrote:
On Mon, Dec 20, 2010 at 4:08 PM, Arun Ranganathana...@mozilla.com wrote:
On 12/20/10 5:38 PM, Jian Li wrote:
On Mon, Dec 20, 2010 at 2:10 PM, Ian
On Mon, Dec 20, 2010 at 5:49 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 12/20/10 7:42 PM, Glenn Maynard wrote:
Has a hash functions API been considered, so browsers can expose, for
example, a native SHA-1 implementation? Doing this in JS is possible,
but painfully slow, even with current
On Tue, 21 Dec 2010, Arun Ranganathan wrote:
I've bolstered the lifetime conformance language with this:
http://dev.w3.org/2006/webapi/FileAPI/#lifeTime
Just one minor nit, the unloading document cleanup steps get called both
when unloading a document and when discarding a document, and may
On Tue, Dec 21, 2010 at 11:31 AM, Arun Ranganathan a...@mozilla.com wrote:
I have updated the editor's draft of the File API (special winter solstice
edition).
In particular:
On 12/20/10 8:32 PM, Michael Nordman wrote:
On Mon, Dec 20, 2010 at 4:08 PM, Arun Ranganathana...@mozilla.com
On Tue, Dec 21, 2010 at 11:31 AM, Arun Ranganathan a...@mozilla.com wrote:
There are more rigid conformance requirements around lastModifiedDate.
http://dev.w3.org/2006/webapi/FileAPI/#dfn-lastModifiedDate
The last modified date of the file; on getting, this MUST return a
Date object [HTML5]
On 12/21/10 4:08 PM, Tab Atkins Jr. wrote:
On Tue, Dec 21, 2010 at 11:31 AM, Arun Ranganathana...@mozilla.com wrote:
There are more rigid conformance requirements around lastModifiedDate.
http://dev.w3.org/2006/webapi/FileAPI/#dfn-lastModifiedDate
The last modified date of the file; on
On 12/21/10 4:07 PM, Michael Nordman wrote:
On Tue, Dec 21, 2010 at 11:31 AM, Arun Ranganathana...@mozilla.com wrote:
I have updated the editor's draft of the File API (special winter solstice
edition).
In particular:
On 12/20/10 8:32 PM, Michael Nordman wrote:
On Mon, Dec 20, 2010 at 4:08
It's actually a bug in Firefox[1] which unfortunately been around for a very
long time, since 2003, and isn't isolated just on the input event it also
affects the invalid event. For detecting events kangax has created a handy
method called isEventSupported[2] which will detect 99% of events
I read Kangax's post, but I hadn't actually seen the tool on github, thanks
for that.
The way that one would hope Fx might support it is by providing an oninput
method on the INPUT element and allowing you to support it that way.
However, regardless of whether this is a bug in Fx or not, the
How 'bouts a shorter version of Tab's suggestion: Web Components ?
On Thu, Dec 16, 2010 at 5:59 AM, Anne van Kesteren ann...@opera.com wrote:
On Thu, 16 Dec 2010 14:51:39 +0100, Robin Berjon ro...@berjon.com wrote:
On Dec 14, 2010, at 22:24 , Dimitri Glazkov wrote:
Looking at the use cases
On Tue, Dec 21, 2010 at 2:58 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Notice that all three of the OP's use-cases were based on checksumming
files. I don't know how reading in a Blob and then hashing it would
compare to just hashing an equivalent string, but I suspect it would
have a
On Tue, Dec 21, 2010 at 2:31 PM, Arun Ranganathan a...@mozilla.com wrote:
I've bolstered the lifetime conformance language with this:
http://dev.w3.org/2006/webapi/FileAPI/#lifeTime
The only nagging doubt I have about this proposal is that the creation and
revocation methods (static) are on
On Tue, Dec 21, 2010 at 4:12 PM, Glenn Maynard gl...@zewt.org wrote:
On Tue, Dec 21, 2010 at 2:31 PM, Arun Ranganathan a...@mozilla.com wrote:
I've bolstered the lifetime conformance language with this:
http://dev.w3.org/2006/webapi/FileAPI/#lifeTime
The only nagging doubt I have about this
I like Web Components.
-- Dirk
On Tue, Dec 21, 2010 at 3:34 PM, Alex Russell slightly...@google.com wrote:
How 'bouts a shorter version of Tab's suggestion: Web Components ?
On Thu, Dec 16, 2010 at 5:59 AM, Anne van Kesteren ann...@opera.com wrote:
On Thu, 16 Dec 2010 14:51:39 +0100, Robin
On Tue, Dec 21, 2010 at 7:17 PM, Jonas Sicking jo...@sicking.cc wrote:
The solution is to instead pass the Blob object to the worker and
inside the worker call URL.createObjectURL(blob). That way you get a
URL whose lifetime is tied to that of the worker.
But yes, if you've lost track of the
17 matches
Mail list logo
