On Tue, Jun 7, 2011 at 11:30 AM, Israel Hilerio wrote:
> On Tuesday, June 07, 2011 1:13 AM, Jonas Sicking wrote:
>> Actually, WebIDL just changed from turning null into "null" to turning null
>> into "". Turns out that a bunch of functions depended on that behavior and
>> so it seems like that's w
On Monday, June 06, 2011 1:48 PM, Jonas Sicking wrote:
> On Mon, Jun 6, 2011 at 10:20 AM, Israel Hilerio
> wrote:
> > What about this:
> >
> > The default value for the range will be null which implies:
> > IDBKeyRange.lower = undefined
> > IDBKeyRange.upper = undefined
> > IDBKeyRange.lowerOpen =
Israel Hilerio:
> What I meant was that on the method description of
> IDBDatabase.setVersion, there is a table that has a nullable column.
> In it the "version" parameter there is an "x" in the Nullable column,
> which implies that the "version" parameter cannot be nullable. I'm
> guessing we want
On Tuesday, June 07, 2011 2:44 PM, Cameron McCormack wrote:
> Israel Hilerio:
> > Are we saying that we should remove the "TreatNullAs=EmptyString" and
> > keep the parameter restriction that "version" cannot be nullable?
>
> The [TreatNullAs=EmptyString] behaviour is now the default, so you
> def
From: dgro...@google.com [mailto:dgro...@google.com] On Behalf Of David Grogan
Sent: Tuesday, June 07, 2011 1:01 PM
>> We (chrome) are still having internal discussions about evictable vs
>> non-evictable storage; we're on board with worrying about this in v2.
>> On Tue, May 31, 2011 at 5:33 PM,
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11350
Pablo Castro changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
timeless:
> would having a field: "mandatory" which indicates which arguments (or
> feature names) must be supported by the implementation assuage your
> concern?
>
> createObjectStore("car", { mandatory: ["foreignKeys"], keyPath: "id",
> foreignKeys: [{keyPath: "brand", objectStore: "car-brands"}
On Tue, Jun 7, 2011 at 5:03 PM, Jonas Sicking wrote:
> For example, say that we in version 2 of indexedDB add support for
> foreign keys. So that you can say:
>
> createObjectStore("car", { keyPath: "id", foreignKeys: [{keyPath:
> "brand", objectStore: "car-brands"}]);
> It seems bad that if a us
Israel Hilerio:
> Are we saying that we should remove the "TreatNullAs=EmptyString" and
> keep the parameter restriction that "version" cannot be nullable?
The [TreatNullAs=EmptyString] behaviour is now the default, so you
definitely want to remove it. When you say “keep the parameter
restriction
On Tue, Jun 7, 2011 at 11:51 AM, Jian Li wrote:
>
>
> On Tue, Jun 7, 2011 at 11:23 AM, Jonas Sicking wrote:
>>
>> On Tue, Jun 7, 2011 at 10:43 AM, Jian Li wrote:
>> > I have a couple questions regarding abort behavior.
>> >
>> > If the reading is completed and the loadend event has been fired, d
On Tue, Jun 7, 2011 at 11:26 AM, Israel Hilerio wrote:
> On Monday, June 06, 2011 3:25 PM, Cameron McCormack wrote:
>> Jonas Sicking:
>> > I don't know about other APIs. But it does seem very unfortunate to
>> > simply silently ignore unknown arguments to
>> > IDBDatabase.createObjectStore. Though
We (chrome) are still having internal discussions about evictable vs
non-evictable storage; we're on board with worrying about this in v2.
On Tue, May 31, 2011 at 5:33 PM, Jonas Sicking wrote:
> On Tue, May 31, 2011 at 3:46 PM, Pablo Castro
> wrote:
> > We discussed evictable stores some time a
On Tue, Jun 7, 2011 at 4:40 PM, Scott Wilson
wrote:
> I'm having a go at implementing the defaultlocale attribute, but have a
> problem with the test cases - these all use defaultlocale="x-w3c-test".
> The problem is that this is a private use code, and so converts to
> "und-x-w3c-test" during pro
On Tue, 7 Jun 2011, Adrian Bateman wrote:
> On Tuesday, June 07, 2011 10:36 AM, Ian Hickson wrote:
> > On Tue, 7 Jun 2011, Adrian Bateman wrote:
> > > We have removed onerror from our implementation since the previous
> > > change and it's frustrating trying track against the spec with
> > > unex
On 13 May 2011, at 16:06, Marcos Caceres wrote:
> Hi,
>
> I changed dlocuse00 to use the language tag "xx" instead of "en-gb"...
>
> http://dev.w3.org/2006/waf/widgets/test-suite/test-cases/ta-defaultlocale-usage/000/ta-de-000.wgt
I've tried this one but don't really understand it. I thought
On Tue, Jun 7, 2011 at 11:23 AM, Jonas Sicking wrote:
> On Tue, Jun 7, 2011 at 10:43 AM, Jian Li wrote:
> > I have a couple questions regarding abort behavior.
> >
> > If the reading is completed and the loadend event has been fired, do we
> want
> > to fire loadend event again when abort() meth
On Tuesday, June 07, 2011 1:13 AM, Jonas Sicking wrote:
> Actually, WebIDL just changed from turning null into "null" to turning null
> into "". Turns out that a bunch of functions depended on that behavior and
> so it seems like that's what we'll be stuck with.
>
> In any case, I think IndexedDB
On Monday, June 06, 2011 3:25 PM, Cameron McCormack wrote:
> Jonas Sicking:
> > I don't know about other APIs. But it does seem very unfortunate to
> > simply silently ignore unknown arguments to
> > IDBDatabase.createObjectStore. Though then again, extra (and thus
> > unknown) arguments are ignore
On Tue, Jun 7, 2011 at 10:43 AM, Jian Li wrote:
> I have a couple questions regarding abort behavior.
>
> If the reading is completed and the loadend event has been fired, do we want
> to fire loadend event again when abort() method is called?
No
> Do we want to reset error to null or leave it i
From: Jonas Sicking [mailto:jo...@sicking.cc]
Sent: Tuesday, May 31, 2011 5:34 PM
>> On Tue, May 31, 2011 at 3:46 PM, Pablo Castro
>> wrote:
>> > We discussed evictable stores some time ago and captured it in bug 11350
>> > [1], but I haven't seen further discussion on it and it hasn't gone in
On Tuesday, June 07, 2011 10:36 AM, Ian Hickson wrote:
> On Tue, 7 Jun 2011, Adrian Bateman wrote:
> > We have removed onerror from our implementation since the previous
> > change and it's frustrating trying track against the spec with
> > unexpected updates.
>
> That's the cost of being on the
I have a couple questions regarding abort behavior.
- If the reading is completed and the loadend event has been fired, do we
want to fire loadend event again when abort() method is called?
- Do we want to reset error to null or leave it intact when abort()
method is called?
Thanks,
On June 7 WebApps published LCWDs of 3 widget specs:
1. Widget Packaging & XML Configuration
http://www.w3.org/TR/2011/WD-widgets-20110607/
2. Widget Interface
http://www.w3.org/TR/2011/WD-widgets-apis-20110607/
3. Widget Digital Signature
http://www.w3.org/TR/2011/WD-widgets-di
On Tue, 7 Jun 2011, Adrian Bateman wrote:
>
> This check-in [1] reintroduces the onerror handler that was removed
> previously [2]. Since, in general, WebSocket protocol errors are fatal
> and result in onclose, what is the purpose of adding this back?
Ian asked me to put it back so that authors
I'm having a go at implementing the defaultlocale attribute, but have a problem
with the test cases - these all use defaultlocale="x-w3c-test".
The problem is that this is a private use code, and so converts to
"und-x-w3c-test" during processing. By default I don't even allow BCP
extensions in
This check-in [1] reintroduces the onerror handler that was removed previously
[2].
Since, in general, WebSocket protocol errors are fatal and result in onclose,
what is
the purpose of adding this back? We have removed onerror from our implementation
since the previous change and it's frustrating
On Thu, 02 Jun 2011 18:25:18 +0200, Arthur Barstow
wrote:
Hi All,
The comment period for Progress Events LC ended on June 1 and my take on
the status is: no comments were submitted to public-webapps during the
LC comment period; there are no open bugs for this spec (Webapps has no
rela
Actually, WebIDL just changed from turning null into "null" to turning
null into "". Turns out that a bunch of functions depended on that
behavior and so it seems like that's what we'll be stuck with.
In any case, I think IndexedDB should be silent on the issue and
simply rely on WebIDL defaults.
28 matches
Mail list logo
