Re: [W3C TCP and UDP Socket API]: Status and home for this specification

2015-04-02 Thread Jeffrey Yasskin
It seems like a CG is appropriate for the Sockets API. It's not clear that a browser is going to adopt it unless the Trust & Permissions CG comes up something, but if more native platforms like Cordova and FFOS want to coordinate on a shared interface, a CG is a good place to iterate on that. If it

Re: [W3C TCP and UDP Socket API]: Status and home for this specification

2015-04-01 Thread Jeffrey Yasskin
Hi all. You've mistakenly cc'ed my father on this thread. Here's my address. On Wed, Apr 1, 2015 at 2:22 AM, Nilsson, Claes1 < claes1.nils...@sonymobile.com> wrote: > Hi all, > > > > Related to the recent mail thread about the SysApps WG and its > deliverables I would like to make a report of the

Re: Proposal for a Permissions API

2015-03-22 Thread Jeffrey Yasskin
pts/ > > Permission/Security prompts are bad UX. Particularly the kind you need to > prompt the user with along the way. And within that, even worse are the ones > that pop up again and again (like the fullscreen popup). > > On Wed, Oct 1, 2014 at 7:34 PM, Jeffrey Yasskin wrote: &

Re: Proposal for a Permissions API

2014-10-01 Thread Jeffrey Yasskin
On Wed, Sep 3, 2014 at 3:29 AM, Mounir Lamouri wrote: > On Wed, 3 Sep 2014, at 04:41, Jonas Sicking wrote: >> I'm generally supportive of this direction. >> >> I'm not sure that that the PermissionStatus thing is needed. For >> example in order to support bluetooth is might be better to make the >

[push] Consider renaming "push notification" to "push message" in the Push API spec

2014-03-10 Thread Jeffrey Yasskin
livered by a push notification (https://dvcs.w3.org/hg/push/raw-file/tip/index.html#pushmessage-interface), it seems like "push message" would be a good replacement for the current ambiguous name. Thanks, Jeffrey Yasskin P.S. I'm not subscribed to public-webapps@, so please cc me if you want me to reply.