On Mon, 19 Oct 2009, Charles McCathieNevile wrote:
> On Mon, 19 Oct 2009 06:43:18 +0200, Ian Hickson wrote:
> > On Mon, 19 Oct 2009, Charles McCathieNevile wrote:
> > >
> > > OK, I'll work on it to try and get an editor's draft out tomorrow.
> > > My rough idea is that you can send an event whic
On Mon, 19 Oct 2009 10:24:37 +0200, Ian Hickson wrote:
> So in a hypothetical system that gives progress for multiple large
> files in a row, you can't have a case where some of the files have
> unknown sizes?
Yes, you can.
How?
If I understand Chaals' proposal correctly, you'd set lengthC
On Mon, 19 Oct 2009, Simon Pieters wrote:
> On Mon, 19 Oct 2009 10:24:37 +0200, Ian Hickson wrote:
> > > >
> > > > So in a hypothetical system that gives progress for multiple large
> > > > files in a row, you can't have a case where some of the files have
> > > > unknown sizes?
> > >
> > > Ye
On Mon, 19 Oct 2009 11:38:27 +0200, Ian Hickson wrote:
On Mon, 19 Oct 2009, Simon Pieters wrote:
On Mon, 19 Oct 2009 10:24:37 +0200, Ian Hickson wrote:
> > >
> > > So in a hypothetical system that gives progress for multiple large
> > > files in a row, you can't have a case where some of the
On Sun, 18 Oct 2009 17:48:04 +0200, Charles McCathieNevile
wrote:
On Sun, 27 Sep 2009 21:04:04 +0200, Charles McCathieNevile
I propose to add the attributes totalItems and loadedItems to preogress
events, as a way of dealing with use cases like showing progress in
downloading an applica
We seem to come from different angles, and our objective may not the
same as
yours. This is not an official statement, but I could formulate our
objective like this:
"How do I enable richer web applications in a touch-aware browser while
still retaining the possibility to interact with existin
On Mon, 19 Oct 2009 18:30:31 +0200, Charles McCathieNevile
wrote:
On Sun, 18 Oct 2009 17:48:04 +0200, Charles McCathieNevile
wrote:
On Sun, 27 Sep 2009 21:04:04 +0200, Charles McCathieNevile
I propose to add the attributes totalItems and loadedItems to preogress
events, as a way of deali
In Step 5 [1], the spec reads:
"If this range begins with the subtag "i", "x", or the range is marked
as "deprecated" in the IANA Language Subtag Registry, skip all the
steps in this algorithm below, and move onto the next range."
I believe that, at least, we should allow "x" (as in "x-secret-lan
On Oct 19, 2009, at 3:29 PM, ext Marcos Caceres wrote:
In Step 5 [1], the spec reads:
"If this range begins with the subtag "i", "x", or the range is marked
as "deprecated" in the IANA Language Subtag Registry, skip all the
steps in this algorithm below, and move onto the next range."
I believ
On 10/19/09 8:56 PM, João Eiras wrote:
> to manipulate the objects you have on your device/OS.
Pan is scrolling for which browsers already fire events. The behavior
for the scroll event would need to change though, so it would be fired
before the event, and be cancelable.
Well, scroll event indi
I posted something about this in the whatwg list and was told to bring it
here.
Currently, AFAIK, the only way to do animation in HTML5 + JavaScript is
using setInterval. That's great but it has the problem that even when the
window is minimized or the page is not the front tab, JavaScript has no
FYI, the original WhatWG thread:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-October/thread.html#23625
On Mon, Oct 19, 2009 at 1:51 PM, Gregg Tavares wrote:
> I posted something about this in the whatwg list and was told to bring it
> here.
>
> Currently, AFAIK, the only way to do an
Apologies for the delay, I've been spending the majority of my time
completing the initial implementation for Chrome, but I've posted a draft
version of a spec for notifications to
http://sites.google.com/a/chromium.org/dev/developers/design-documents/desktop-notifications/api-specification
I thin
I have a proposal for solving this here:
http://groups.google.com/group/mozilla.dev.platform/browse_thread/thread/527d0cedb9b0df7f/57625c94cdf493bf
The gist is very simple:
1) window.requestAnimationFrame(): Signals that an animation is in progress,
and requests that the browser schedule a repaint
Pan is scrolling for which browsers already fire events. The behavior
for the scroll event would need to change though, so it would be fired
before the event, and be cancelable.
Well, scroll event indicates that something has been scrolled. So we
shouldn't change its behavior.
Pan is closer t
On Mon, 19 Oct 2009 22:11:50 +0200, Olli Pettay
wrote:
On 10/19/09 8:56 PM, João Eiras wrote:
...
Therefore they should be completely
separate from any kind of mouse event feature. Obviously, the scroll and
zoom events would need a target which would be the element with focus,
Why the eleme
ISSUE-107 (multi-object end events): End state events in multi-object
transactions [Progress Events]
http://www.w3.org/2008/webapps/track/issues/107
Raised by: Charles McCathieNevile
On product: Progress Events
Where a transaction has multiple objects (i.e. there is a loadedItems attribute
pr
Hi folks,
I committed a new draft[1] which incorporates my proposals for resolving
ISSUE-105 (adding loadedItems and totalItems and trying to explain what
happens when they are there. It also notes, but doesn't yet provide any
solution for ISSUE-107 - I will think about it tomorrow.
The changelo
On Mon, 19 Oct 2009 20:13:23 +0200, Anne van Kesteren
wrote:
On Mon, 19 Oct 2009 18:30:31 +0200, Charles McCathieNevile
wrote:
On Sun, 18 Oct 2009 17:48:04 +0200, Charles McCathieNevile
wrote:
On Sun, 27 Sep 2009 21:04:04 +0200, Charles McCathieNevile
I propose to add the attributes t
I'd like to revive the "Proposal for sending multiple files via
XMLHttpRequest.send()" thread
started by Jian Li back in September.
As pointed out on that thread, sending a JS array of strings and File
references isn't going
to fly due to an array of strings already having meaning.
That thread co
20 matches
Mail list logo
