On 11/15/12 7:39 PM, ext Eric U wrote:
As discussed at TPAC, there's little support for the current FileSystem API, but
some support for a new API, and I promised to put forth a compromise proposal.
In order to do that, I'd like to hear 1) what kinds of changes would make it
more popular; 2) who
-Original Message-
From: Arthur Barstow [mailto:art.bars...@nokia.com]
Sent: Friday, November 30, 2012 6:46 AM
To: ext Eric U; Doug Schepers
Cc: Web Applications Working Group WG
Subject: Re: FileSystem compromise spec
On 11/15/12 7:39 PM, ext Eric U wrote:
As discussed at TPAC,
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20148
Anne ann...@annevk.nl changed:
What|Removed |Added
Status|NEW |RESOLVED
On Thu, Nov 8, 2012 at 6:37 AM, Hallvord Reiar Michaelsen Steen wrote:
Hence, what I think would be most usable in the real world would be
making event.key a mapping back to un-shifted character values of a
normal QUERTY (en-US) layout. Authors are asking for stable reference
values for
A spec oddity that we noticed - if you explicitly close a connection during
an upgradeneeded handler (or elsewhere in the transaction), the transaction
should complete (not abort) yet the connection fails (error), upgrading the
database but leaving you without a connection.
Example:
var req =
Awesome stuff Gary.
(And I like that we won't need to change the behavior of key or char in your
proposal—that part made me really nervous, since IE has shipped this stuff
since 9, and I know our new Win8 app model is using it.)
I'm planning in the short term to start a new DOM4 Events spec,
On Fri, Nov 30, 2012 at 4:29 PM, Travis Leithead
travis.leith...@microsoft.com wrote:
Awesome stuff Gary.
** **
(And I like that we won't need to change the behavior of key or char in
your proposal—that part made me really nervous, since IE has shipped this
stuff since 9, and I know
