On 4/21/10 1:51 AM, Jian Li wrote:
According to the spec, we will dispatch a progress event for a read
method. But per the "Progress Events 1.0" spec, the attributes "loaded"
and "total" are defined as "unsigned long".
interface ProgressEvent : events::Event {
...
readonly
On 4/21/10 1:51 AM, Jian Li wrote:
According to the spec, we will dispatch a progress event for a read
method. But per the "Progress Events 1.0" spec, the attributes "loaded"
and "total" are defined as "unsigned long".
interface ProgressEvent : events::Event {
...
readonly
The current version of File API does not refer to the latest version of
ProgressEvent and thus I am seeing "unsigned long", instead of "unsigned
long long" being used.
Certainly for "unsigned long long", we could only treat it as EMCAScript
Number types not greater than 2^53.
On Mon, Apr 26, 2010
On Tue, Apr 20, 2010 at 4:22 PM, Jonas Sicking wrote:
> On Tue, Apr 20, 2010 at 3:51 PM, Jian Li wrote:
> > According to the spec, we will dispatch a progress event for a read
> method.
> > But per the "Progress Events 1.0" spec, the attributes "loaded" and
> "total"
> > are defined as "unsigne
On Tue, Apr 20, 2010 at 3:51 PM, Jian Li wrote:
> According to the spec, we will dispatch a progress event for a read method.
> But per the "Progress Events 1.0" spec, the attributes "loaded" and "total"
> are defined as "unsigned long".
> interface ProgressEvent : events::Event {
> ..
According to the spec, we will dispatch a progress event for a read method.
But per the "Progress Events 1.0" spec, the attributes "loaded" and "total"
are defined as "unsigned long".
interface ProgressEvent : events::Event {
...
readonly attribute unsigned long loaded;
