Whomever adds delete/continue back to the spec needs to inline into
the spec an explanation of why it's ok per ES5.
Most (all) of us grew up pre ES5 and *believe* that they're truly
reserved keywords and that what you're doing is invalid.
So without inlining the explanation into the spec, you're
I realize that the HTML Device element [1] is still in its infancy but
should the scope of this spec be modified to integrate with other APIs as
proposed here:
http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0026.html
?
The proposed device element seems like the most logical fit
I think I'm asking this question in the wrong place and so I'm re-posting to
the more appropriate public-html-comments list.
** Please be sure to remove public-webapps@w3.org from any replies to avoid
cross-posting **
- Richard
On Tue, Jul 6, 2010 at 12:41 PM, Rich Tibbett
On Tue, 06 Jul 2010 13:41:27 +0200, Rich Tibbett rich.tibb...@gmail.com
wrote:
I know first hand that we don't deal in roadmaps, but should we assign
some priority to fleshing out such a fundamental element as device?
device was proposed to the DAP WG, not the WebApps WG. Other than that
Anne has now integrated the CR's exit criteria and text about security
considerations into the version proposed for CR:
[[
http://dev.w3.org/2006/webapi/XMLHttpRequest/#crec
Candidate Recommendation Exit Criteria
To exit the Candidate Recommendation (CR) stage the following criteria
must
On Tue, Jul 6, 2010 at 5:18 AM, Anne van Kesteren ann...@opera.com wrote:
There are some advantages with input, but overall the design is ugly.
input type=file is buffered, which would seem to exclude the
possibility of onchange=form.submit() in any of its forms' elements,
but is otherwise
The public-web-notification Mail List was created for the Web
Notifications spec and the ML's archive is available at:
http://lists.w3.org/Archives/Public/public-web-notification/
The above includes a subscribe to this list link.
Original Message
Subject:[Work in
Nikunj, Jonas, All,
Chaals, the Team and I all support this proposal. Thanks to you both!
-Art Barstow
From: public-webapps-requ...@w3.org [public-webapps-requ...@w3.org] On Behalf
Of ext Nikunj Mehta [nik...@o-micron.com]
Sent: Tuesday, July 06, 2010
+1
On Tue, Jul 6, 2010 at 4:11 PM, art.bars...@nokia.com wrote:
Nikunj, Jonas, All,
Chaals, the Team and I all support this proposal. Thanks to you both!
-Art Barstow
From: public-webapps-requ...@w3.org [public-webapps-requ...@w3.org] On
Behalf
On Tue, Jul 6, 2010 at 9:36 AM, Nikunj Mehta nik...@o-micron.com wrote:
Hi folks,
There are several unimplemented proposals on strengthening and
expanding IndexedDB. The reason I have not implemented them yet is
because I am not convinced they are necessary in toto. Here's my
attempt at
On Wed, Jul 7, 2010 at 5:57 AM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Jul 6, 2010 at 9:36 AM, Nikunj Mehta nik...@o-micron.com wrote:
Hi folks,
There are several unimplemented proposals on strengthening and
expanding IndexedDB. The reason I have not implemented them yet is
Sounds great!
On Wed, Jul 7, 2010 at 12:39 AM, Nikunj Mehta nik...@o-micron.com wrote:
Hi folks,
I would like to propose adding Jonas Sicking to the list of editors
for the IndexedDB spec. Many of you have seen the tremendous amount of
work Jonas has done to assist in finalizing the
12 matches
Mail list logo
