http://www.w3.org/Bugs/Public/show_bug.cgi?id=14120
Summary: Current spec for EventSource close method doesn't
defined behaviour when close called after 'onopen' or
'onmessage'. For example, Google Chrome, closes
connection if
On Fri, Jun 24, 2011 at 4:27 PM, Kenneth Russell wrote:
> On Fri, Jun 24, 2011 at 3:43 PM, Ian Hickson wrote:
>> On Fri, 24 Jun 2011, Kenneth Russell wrote:
>>>
>>> Slightly larger issue. In the typed array spec, views like Float32Array
>>> refer to an ArrayBuffer instance. It's desired to be abl
Based on previous conversations, it seems we've agreed that there are
situations in which a transaction could failed independent of explicit requests
(i.e. QUOTA_ERR, TIMEOUT_ERR). We believe that this can be represented as an
implicit request that is being triggered by a transaction. We would
On Monday, September 12, 2011 1:56 PM, Israel Hilerio wrote:
> On Sunday, September 04, 2011 3:33 AM, Jonas Sicking wrote:
> > Hi Everyone,
> >
> > I finally got around to updating the IndexedDB spec to the new version API!
> > Definitely a non-trivial change, so I'd love for people to have a look
I've updated the draft spec http://goo.gl/9G8pd with these points.
- Removed Touch related components to simplify initial version of
specification and because they do not add the same level of new application
capability as mouse related events.
- MouseLockable Interface moved from element to docum
On Friday, September 02, 2011 3:33 AM, Hans Wennborg wrote:
> -Original Message-
> From: Hans Wennborg [mailto:hwennb...@google.com]
> Sent: Friday, September 02, 2011 3:33 AM
> To: Israel Hilerio
> Cc: public-webapps@w3.org; Jim Wordelman; Dany Joly; Adam
> Herchenroether; Victor Ngo
> Sub
On Sunday, September 04, 2011 3:33 AM, Jonas Sicking wrote:
> Hi Everyone,
>
> I finally got around to updating the IndexedDB spec to the new version API!
> Definitely a non-trivial change, so I'd love for people to have a look at it
> to
> see if I messed anything up.
>
> I decided to go with t
As indicated a few months ago [1], WebApps will have a f2f meeting
during the October 31 - November 4 "TPAC" week:
http://www.w3.org/2008/webapps/wiki/TPAC2011
We have a room reserved for Monday October 31 and Tuesday November 1. If
you have any specific agenda requests, please send them to
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14119
Summary: Strip collapsed whitespace on insertText
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
On Thu, Sep 8, 2011 at 8:14 PM, Tim Down wrote:
> I'd suggest the DOM Range tests in ACID3 could be modified to test
> against the newer WHATWG Range spec, which clears up some ambiguities
> in the DOM 2 Range spec (there's one about what happens to Range
> boundaries after a particular insertNode
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13104
Iñaki Baz Castillo changed:
What|Removed |Added
Status|RESOLVED|REOPENED
CC|
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14116
Summary: Regarding a previous post, a browser could launch
itself (CreateProcess() on Windows) again and pass say
a port number, a URL, and a boolean flag to the
spawned child
12 matches
Mail list logo