On Oct 18, 2010, at 6:18 PM, Oliver Hunt wrote:
On Oct 18, 2010, at 6:11 PM, Cameron McCormack wrote:
Erik Arvidsson:
The problem is that trying to get a non existing property in JS should
return undefined. Not null and not an empty string. I understand that
the spec used null since
On Tue, 19 Oct 2010 02:30:39 +0200, Jonas Sicking jo...@sicking.cc wrote:
I agree. Another thing that is nice about the window.*BlobURL() API is
that it makes it clear which origin the created url will have. I.e.
the origin of the window which it's called on.
We could maintain that even if we
On Mon, 18 Oct 2010 20:15:53 +0200, Jonas Sicking jo...@sicking.cc wrote:
Without revoking the UA has to keep around the URL-string - resource
mapping for the lifetime of the page. Which in the world of web apps
can be a very long time. Even worse, in the case of dynamically
created blobs
On Tue, 19 Oct 2010 03:11:25 +0200, Cameron McCormack c...@mcc.id.au
wrote:
Does it particularly matter that collection.item(999) returns null while
collection['999'] evaluates to undefined? To me, it makes sense enough.
Functions and properties that returns Nodes, and which have no Node to
Reminder: October 26 is the deadline for comments for the October 5
LCWD of the Widget PC spec.
On Oct/5/2010 12:33 PM, ext Arthur Barstow wrote:
This is a Request for Comments for the October 5 Last Call Working
Draft (LCWD) of the Widget Packaging and Configuration spec:
All
Here are some of the comments on http://www.w3.org/TR/widgets/ W3C
Working Draft 5 October 2010
1. 7.9.2. The email Attribute
mentions that email is a keyword attribute where
A keyword is a string that is reserved for the purpose of this
specification. The value of a keyword attribute
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11094
Summary: [IndexedDB] IDBIndex.get* don't define which item is
returned in the case of duplicates
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
On 10/19/10 4:20 AM, Anne van Kesteren wrote:
On Tue, 19 Oct 2010 02:30:39 +0200, Jonas Sicking jo...@sicking.cc
wrote:
I agree. Another thing that is nice about the window.*BlobURL() API is
that it makes it clear which origin the created url will have. I.e.
the origin of the window which it's
ISSUE-150: [widgets] Email and param name and value as 'Keyword attributes' is
causing confusion in Widgets PC Spec
http://www.w3.org/2008/webapps/track/issues/150
Raised by:
On product:
ISSUE-151: [widgets] PC Spec If feature-name is not a valid IRI, and
required-feature is true, then the user agent must treat this widget as an
invalid widget package. but doesnt say anything about the case when it is not
required.
http://www.w3.org/2008/webapps/track/issues/151
Raised
ISSUE-152: [widgets] PC test suite needs a few more XML entity cases to check
for well-formed XML
http://www.w3.org/2008/webapps/track/issues/152
Raised by:
On product:
On 10/18/10, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/18/10 9:34 PM, Garrett Smith wrote:
\.item\(\d+\s*\)\s*===\s*null lang:javascript
Doesn't catch cases when the argument to item is not a numeric constant,
most simply.
Or a reference like `i`, `foo.bar`, `f[d]`, `f[ d ]`
On 10/19/10, Anne van Kesteren ann...@opera.com wrote:
On Tue, 19 Oct 2010 03:11:25 +0200, Cameron McCormack c...@mcc.id.au
wrote:
Does it particularly matter that collection.item(999) returns null while
collection['999'] evaluates to undefined? To me, it makes sense enough.
Functions and
On Tue, Oct 19, 2010 at 09:50, Garrett Smith dhtmlkitc...@gmail.com wrote:
...
CSSStyleDeclaration. What about the other collection objects? HTML5
says that collections are now callable and specifies that indexed
property access on collections returns null. But what about other APIs
such as
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11097
Summary: [IndexedDB] Behavior of .close() is not completely
specified
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Seems to me that when you access a slot that in some sense doesn't exist
it should return undefined, not null. There are plenty of semantic cases (is
this attribute defined but currently unset, or not defined at all) where the
difference can be significant. I realize not all languages support the
On 10/19/10, Scott Shattuck idea...@mindspring.com wrote:
Seems to me that when you access a slot that in some sense doesn't exist
it should return undefined, not null. There are plenty of semantic cases (is
this attribute defined but currently unset, or not defined at all) where the
Jonas just checked in a change to replace .remove() with .delete() (amongst
other changes we agreed upon a while ago). In light of that, does it make
sense for removeIndex and removeObjectStore to be renamed to deleteIndex and
deleteObjectStore to match the new naming? I don't care a whole lot,
On Tue, Oct 19, 2010 at 1:24 AM, Anne van Kesteren ann...@opera.com wrote:
On Mon, 18 Oct 2010 20:15:53 +0200, Jonas Sicking jo...@sicking.cc wrote:
Without revoking the UA has to keep around the URL-string - resource
mapping for the lifetime of the page. Which in the world of web apps
can be
On Tue, Oct 19, 2010 at 3:39 PM, Jeremy Orlow jor...@chromium.org wrote:
Jonas just checked in a change to replace .remove() with .delete() (amongst
other changes we agreed upon a while ago). In light of that, does it make
sense for removeIndex and removeObjectStore to be renamed to
On Tue, Oct 19, 2010 at 3:39 PM, Jeremy Orlow jor...@chromium.org wrote:
Jonas just checked in a change to replace .remove() with .delete() (amongst
other changes we agreed upon a while ago). In light of that, does it make
sense for removeIndex and removeObjectStore to be renamed to
On Tue, Oct 19, 2010 at 1:20 AM, Anne van Kesteren ann...@opera.com wrote:
On Tue, 19 Oct 2010 02:30:39 +0200, Jonas Sicking jo...@sicking.cc wrote:
I agree. Another thing that is nice about the window.*BlobURL() API is
that it makes it clear which origin the created url will have. I.e.
the
22 matches
Mail list logo
