Hi,
I agree with Chad's suggestions: the spec should be expanded to expose
more than the core set of axes buttons, and richer metadata would be
extremely useful to developers.
I've been using the gamepad API (as shipped in Chrome, at least - I
haven't had time to adapt to Firefox's
On Wed, Oct 15, 2014 at 2:40 AM, Bogdan Brinza bbri...@microsoft.com wrote:
http://www.w3.org/TR/DOM-Level-3-Events/#trusted-events
That text is utterly broken as we've discussed several times now.
Events do not cause action. Actions cause events (that can then
prevent further action). There is
Hi All,
Mounir would like to publish a new WD of Screen Orientation and the
target date for that publication is October 21:
https://w3c.github.io/screen-orientation/
If anyone has any major concerns about this plan, please speak up as
soon as possible.
-Thanks, AB
https://www.w3.org/Bugs/Public/show_bug.cgi?id=8
Anne ann...@annevk.nl changed:
What|Removed |Added
Status|REOPENED|RESOLVED
-Original Message-
From: annevankeste...@gmail.com [mailto:annevankeste...@gmail.com] On Behalf Of
Anne van Kesteren
On Wed, Oct 15, 2014 at 2:40 AM, Bogdan Brinza bbri...@microsoft.com wrote:
http://www.w3.org/TR/DOM-Level-3-Events/#trusted-events
That text is utterly broken as we've
I replaced the W3C Streams API spec WD with a pointer to the WHATWG Streams
spec and a few sections discussing what we should add to the spec for browser
use cases.
This change means that the W3C Editor’s draft no longer defines the Stream
interface as was previously supported. Would it be
From: Paul Cotton [mailto:paul.cot...@microsoft.com]
Would it be feasible to resurrect this interface as a layer on top of [1] so
that W3C specifications like MSE that have a dependency on the Streams
interface are not broken?
The decision we came to in web apps some months ago was that
The decision we came to in web apps some months ago was that the interfaces
in that spec would disappear in favor of WritableStream, ReadableStream, and
the rest.
This seems to contradict the direction that was published in Feb 2014 [1] in
which it was clearly stated:
In addition to the
On Wed, Oct 15, 2014 at 11:24 AM, Domenic Denicola
dome...@domenicdenicola.com wrote:
From: Paul Cotton [mailto:paul.cot...@microsoft.com]
Would it be feasible to resurrect this interface as a layer on top of
[1] so that W3C specifications like MSE that have a dependency on the
Streams
Hi,
I'm with the IE Platform team at Microsoft. I joined the WebApps WG very
recently. I am looking into the Push API spec, and got some questions. Hope
to get help from experts in the WG.
The current API definition is based on an extension of the Service Workers.
I'd like to understand
I'm not an expert either, but it seems to me that push without service workers
(or some other means of background processing) is basically just server-sent
events. That is, you could send push notifications to an active webpage over
a server-sent events channel (or web socket, or
My understanding here is that we want to leverage the push client in the OS.
That will provide new capabilities without dependency on a direct connection
between the app and the app server.
-Original Message-
From: Domenic Denicola [mailto:dome...@domenicdenicola.com]
Sent: Wednesday,
The hard question is: What do you do if there's an incoming push
message for a given website, but the user doesn't have the website
currently open.
Service Workers provide the primitive needed to enable launching a
website in the background to handle the incoming push message.
Another solution
On 15 October 2014 23:07, Shijun Sun shij...@microsoft.com wrote:
My understanding here is that we want to leverage the push client in the
OS. That will provide new capabilities without dependency on a direct
connection between the app and the app server.
The Push API doesn't use a direct
On 15 October 2014 14:58, Domenic Denicola dome...@domenicdenicola.com wrote:
So from my perspective, implementing the push API without service workers
would be pretty pointless, as it would give no new capabilities.
That's not strictly true. If I sit (as I do) with a tab open to gmail
for a
-Original Message-
From: Travis Leithead
Sent: Wednesday, October 15, 2014 10:53 AM
To: Anne van Kesteren; Bogdan Brinza
Cc: public-webapps@w3.org
Subject: RE: [DOM-Level-3-Events] Synthetic mouse events triggering default
action
-Original Message-
From:
Thanks folks for the quick responses to the questions!
RE: [Martin Thomson] If I sit (as I do) with a tab open to gmail for a very
long time, then it is of some advantage to me (and my network usage) to use
something like push rather than websockets (or even server sent events).
Besides,
17 matches
Mail list logo
