-Original Message-
From: public-webapps-requ...@w3.org [mailto:public-webapps-requ...@w3.org] On
Behalf Of ben turner
Sent: Tuesday, September 28, 2010 8:19 AM
Yes, let's have it tied to the instance on which setVersion() was called.
As Shawn pointed out that is consistent with the
I agree with Jonas on this. I think accessing the index values is an important
feature (in addition to joins you can imagine add an extra property or two to
the index key* to create a covering index and avoid fetching the object in a
perf-critical path).
That said, to me it's just about
From: Jungshik Shin (신정식, 申政湜) [mailto:jungs...@google.com]
Sent: Tuesday, August 24, 2010 10:34 PM
As for the locale identifiers, my understanding is that Windows APIs (newer
'name-based' locale APIs) more or less follows BCP 47.
Picking this back up from this August thread. I went
On Sun, 26 Sep 2010 12:01:59 +0200, Vladimir Dzhuvinov
vladi...@dzhuvinov.com wrote:
I looked at various CORS examples, but they were not particularly
instructional on how the server should respond if the origin is not
allowed or some other check fails. The CORS spec also seems to
deliberately
I added the following slots for November 2:
[[
http://www.w3.org/2008/webapps/wiki/TPAC2010#Tuesday.2C_November_2
13:30-15:00: Indexed DB
15:30-16:30: Indexed DB
16:30-18:00: File * APIs
]]
Of course we can fine-tune the times as needed.
Arun - we reserved a speaker phone for remote
What should we do when setVersion is called while a setVersion transaction
is currently active?
Off the top of my head, I can think of two behaviors we might want to spec:
1) Have the subsequent setVersion simply throw an error. 2) Have the
subsequent setVersion adopt the existing setVersion
On 9/29/2010 6:12 AM, Jeremy Orlow wrote:
Off the top of my head, I can think of two behaviors we might want to spec:
1) Have the subsequent setVersion simply throw an error. 2) Have the
subsequent setVersion adopt the existing setVersion transaction and change
the version. (i.e. whatever
On 29 September 2010 13:48, Anne van Kesteren ann...@opera.com wrote:
On Sun, 26 Sep 2010 12:01:59 +0200, Vladimir Dzhuvinov
vladi...@dzhuvinov.com wrote:
I looked at various CORS examples, but they were not particularly
instructional on how the server should respond if the origin is not
On 9/25/10 7:29 AM, Barstow Art (Nokia-CIC/Boston) wrote:
As with all of our CfCs, positive response is preferred and encouraged
and silence will be assumed to be assent.
Support!
-ArtB
On Wed, Sep 29, 2010 at 6:12 AM, Jeremy Orlow jor...@chromium.org wrote:
What should we do when setVersion is called while a setVersion transaction
is currently active?
Off the top of my head, I can think of two behaviors we might want to spec:
1) Have the subsequent setVersion simply throw
ISSUE-134 (optional useCapture): Consider making useCapture parameter of
add/removeEventListener optional [DOM3 Events]
http://www.w3.org/2008/webapps/track/issues/134
Raised by: Doug Schepers
On product: DOM3 Events
Sergey Ilinsky
11 matches
Mail list logo
