- From: Navid Zolghadr <nzolghadr@chromium.org>
- Date: Tue, 2 Oct 2018 11:43:54 -0400
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: “public-pointer-events@w3.org” <public-pointer-events@w3.org>, Navid Zolghadr <nzolghadr@google.com>, Olli Pettay <opettay@mozilla.com>
- Message-ID: <CAB8=uKb=u1TVz=5j16o2EU-of9D0-46C7BqjBfv4cTefPi-vQA@mail.gmail.com>
Sorry for the delay. I just sent a pull request to address that outstanding issue and a small editorial issue. Regarding the PR, I believe we are all good on Google side. On Mon, Oct 1, 2018 at 5:27 AM Patrick H. Lauke <redux@splintered.co.uk> wrote: > Ping... > > On 22/09/2018 14:30, Patrick H. Lauke wrote: > > Not having heard any objection, I'll assume that the group is happy > > moving forward with PR ? A positive response here, rather than silence, > > would be great, but not mandatory... > > > > Also, we still have https://github.com/w3c/pointerevents/issues/259 > > outstanding. I've not had a chance to deep-dive into what's really > > needed here. Navid, Olli, anybody able to at least make an initial stab > > at this? > > > > Also, in related news, you've probably heard that WebKit are now > > apparently starting development of PE as well... > > https://twitter.com/grorgwork/status/1043302741626376192 (better late > > than never?) > > > > Patrick > > > > On 11/09/2018 11:45, Patrick H. Lauke wrote: > >> Dear all, > >> > >> I'm fairly certain we've had informal agreement for ages that the > >> group is ok to move forward with going to proposed recommendation, but > >> I can't seem to find (in minutes or email threads) an unambiguous vote > >> or decision to that effect. > >> > >> Could I therefore explicitly ask, for process' sake, members of this > >> group to please respond to this email and to indicate whether or not > >> they're happy for us to move PE2 to proposed recommendation? Please > >> respond, if possible, within one week of this email. > >> > >> Additionally, Philippe quite rightly pointed me to a handful of open > >> issues that need to be addressed before we can proceed: > >> > >> * https://github.com/w3c/pointerevents/issues/256 - I see Navid is > >> already on the case here. > >> > >> * https://github.com/w3c/pointerevents/issues/259 - seems like this is > >> just a matter of rewording prose; if so, I'll get on it today. > >> > >> * https://github.com/w3c/pointerevents/issues/254 - I closed this, as > >> I don't think it's a simple/straightforward editorial change to make > >> (unless I'm missing something, this would require either manual > >> addition of CSS classes in the spec itself, or switching to Bikeshed) > >> > >> Thanks, > >> > >> Patrick > > > > > -- > Patrick H. Lauke > > www.splintered.co.uk | https://github.com/patrickhlauke > http://flickr.com/photos/redux/ | http://redux.deviantart.com > twitter: @patrick_h_lauke | skype: patrick_h_lauke > >
Received on Tuesday, 2 October 2018 15:44:28 UTC