Using the onload event is a good idea, but has drawbacks:
1. Some interesting network loads don't generate a load event (XHR,
CSS background image, CSS @import, redirect, object subresource, etc)
2. We'd like lazy loaded analytics scripts to have access to timings
even if they are loaded after
On Wed, 28 Apr 2010 18:48:52 +0200, Gregg Tavares g...@google.com wrote:
Has there been any consideration of switching the spec to a stream-able
format like gzipped tar files? It seems like a shame to miss this use
case.
A streamable container, while intriguing, also has issues. For
On Apr 29, 2010, at 02:36 , Eric Uhrhane wrote:
I agree. Here's what I propose:
FileWriter is needed for the FileSystem API. It's not a great match
for a one-time export of a data Blob from a web app. I think I should
take out all the how do I get a FileWriter stuff that's in [1],
On Thu, Apr 29, 2010 at 3:00 AM, Robin Berjon ro...@berjon.com wrote:
Though admittedly I'm biased because I'm not sold on the whole
FileSystem API and I don't expect anyone will step up and implement it
in firefox anytime soon.
Care to elaborate?
I don't see any significant advantages over
hello:
can we extend some html file as resource in a widget? if can, how to load the
extention html file from the start.html.
btw,what languages we used for ui markup? html+css? if use the html, how deal
with the a tag of html.
thanks.
best regards!
Reminder: May 6 is the deadline for comments re the April 15 LCWD of
the Digital Signatures for Widgets spec:
http://www.w3.org/TR/2010/WD-widgets-digsig-20100415/
Please send comments to public-weba...@w3.org.
Begin forwarded message:
From: Barstow Art (Nokia-CIC/Boston)
On Thu, Apr 29, 2010 at 6:11 AM, Simon Pieters sim...@opera.com wrote:
You mean StorageEvent?
javascript:alert('url' in StorageEvent.prototype)
Opera: false
Firefox: true
Chrome: false
I tried actually causing a storage event and then enumerated its properties
with each browser and got
FYI.
From: Alexandre Bertails berta...@w3.org
Subject: DVCS platform at W3C
Date: April 29, 2010 10:23:55 AM EDT
W3C is pleased to announce the availability of its new Distributed
Version Control System, based on Mercurial [1].
If one wants to request a new repository, just send an email to
On 4/29/10 9:23 AM, Jeremy Orlow wrote:
Opera 10.50 does return false for your bit of javascript, but when I
enumerate the properties on event after causing a storage event, url
is there. Weird.
All that means is that the property is an own property of the object,
not a property
I have fund a number of issues with the dig sig spec:
1. The conformance model is all screwy: it mixes conformance criteria
for too many products (including ones on which were it makes no sense,
like signature documents). The conformance criteria makes the spec
really hard to write test for.
On 4/29/10 12:13 PM, Jeremy Orlow wrote:
The following script does not work for me in 3.6. Would love to know
what I'm doing wrong:
window.onstorage = function() { alert(HI); }
localStorage.foo = localStorage.foo + ;
In Gecko storage events for a change in window X are fired at all
windows
On Thu, Apr 29, 2010 at 6:34 PM, Gregg Tavares g...@google.com wrote:
On Thu, Apr 29, 2010 at 2:52 AM, Arve Bersvendsen ar...@opera.com wrote:
On Wed, 28 Apr 2010 18:48:52 +0200, Gregg Tavares g...@google.com wrote:
Has there been any consideration of switching the spec to a stream-able
On Thu, Apr 29, 2010 at 11:56 AM, Michael Nordman micha...@google.com wrote:
Sounds like we agree on there being a distinction between two levels of
persistence with one being more permanent than the other. Great, provided
we have that agreement we can craft interfaces that allow callers to
On Thu, Apr 29, 2010 at 10:57 AM, Jonas Sicking jo...@sicking.cc wrote:
I think we were operating under the assumption that we're going to
avoid involving the user until neccesary. So for example letting the
site store a few MB of data without the user getting involved, and
only once enough
On 4/29/2010 1:08 PM, Tab Atkins Jr. wrote:
When you say per site do you mean per subdomain, or per domain? The
former is too permissive, the latter is too restrictive.
I believe he means per origin. At least that's what I took from our
discussion.
Cheers,
Shawn
smime.p7s
Description:
On Wed, 28 Apr 2010, Jonas Sicking wrote:
I really think we should make sure we end up with a consistent naming
scheme here. If Gecko is the only engine that's going to do .url
instead of .URL, then I'm happy to change it back (on the assumption
that Gecko will eventually be forced to
2010/4/30 Ian Fette (イアンフェッティ) ife...@google.com:
I remain perplexed by the state of the spec is feature complete and looking
for implementations - potential implementors saying the spec has X,Y,Z
flaws - sorry, the spec is feature complete. We're looking for
implementations. At this rate,
On Thu, Apr 29, 2010 at 7:01 PM, Ian Hickson i...@hixie.ch wrote:
On Wed, 28 Apr 2010, Jonas Sicking wrote:
I really think we should make sure we end up with a consistent naming
scheme here. If Gecko is the only engine that's going to do .url
instead of .URL, then I'm happy to change it
On Thu, Apr 29, 2010 at 6:58 PM, Eric Uhrhane er...@google.com wrote:
On Thu, Apr 29, 2010 at 3:35 AM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Apr 29, 2010 at 3:00 AM, Robin Berjon ro...@berjon.com wrote:
Though admittedly I'm biased because I'm not sold on the whole
FileSystem API and I
19 matches
Mail list logo
