W3C home > Mailing lists > Public > www-style@w3.org > August 2014

Re: Web input brainstorming face-to-face notes

From: Rick Byers <rbyers@chromium.org>
Date: Wed, 20 Aug 2014 12:55:59 -0400
Message-ID: <CAFUtAY9cdMf65Z=QAv5Xj32fMWKDN4-6TpijxL+sEzhn9h_zFA@mail.gmail.com>
To: Jacob Rossi <Jacob.Rossi@microsoft.com>
Cc: "public-touchevents@w3.org" <public-touchevents@w3.org>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>, "www-style@w3.org" <www-style@w3.org>
Right, that was definitely NOT the consensus.  Sorry for the sloppiness in
the notes.  I've updated the summary to make that point clear by adding the
following text:

Google proposes exploring extending touch events with all the good
properties of pointer events - no consensus on this (IE and Firefox teams
feel pointer events are still the better path)


I've also accepted your edits further down.  Hopefully this didn't result
in too much confusion - there were other notes like "This is controversial…
web devs want Pointer Events".  Feel free to propose other edits if it's
still not crystal clear.

Rick



On Wed, Aug 20, 2014 at 12:18 PM, Jacob Rossi <Jacob.Rossi@microsoft.com>
wrote:

>  Hey Rick,
>
> Tab and I were having a conversation the other day and it seems there was
> some confusion about the "consensus" regarding pointer and touch events
> coming out of this meeting. Looking at the latest meeting notes, it does
> indeed look like we all agreed to change our focus to modifying touch
> events to have pointer events features (e.g. fire touch events for mouse,
> etc). While that was Google's proposal, there wasn't consensus that this
> was the correct next step.
>
> Could we update these minutes to clarify this was a Google proposal?
>
> Thanks,
>
> Jacob
>  ------------------------------
> From: Rick Byers <rbyers@chromium.org>
> Sent: ‎7/‎3/‎2014 6:52 AM
> To: public-touchevents@w3.org; public-pointer-events@w3.org;
> www-style@w3.org
> Cc: Jacob Rossi <Jacob.Rossi@microsoft.com>
>
> Subject: Web input brainstorming face-to-face notes
>
>   On June 23rd, a few people from the Firefox, Safari, IE and Chrome
> teams met at Microsoft to brainstorm
> <https://docs.google.com/a/chromium.org/presentation/d/16uP_ofdyXeGXpz4iR1vyi-HDczyAEIH0B3VFI_SxIYY/edit#slide=id.p> [1]
> about opportunities for better collaboration in improving input-related
> APIs (where interoperability has historically been relatively poor).
>
>  Detailed notes from the meeting and links to presentations are here
> <https://docs.google.com/a/chromium.org/document/d/1Bfcw9iR1SF2VYCXBegbqhbqWMim-ZEd7_iaQODE-RPY/edit#>
> [2].
>
>  We identified the following areas as the most promising, and have agreed
> to follow up in the relevant W3C lists:
>
> Speccing mobile viewport behavior [CSSWG]
>  Exposing the visual viewport (eg. device-fixed) [CSSWG]
>  Future of touch events / pointer events [PEWG/TECG]
>  Hover/active rationalization [CSSWG]
>  Scroll response effects [FXTF/TECG]
>  Fractional scroll offsets [CSSWG]
>
>  If you've got questions about any specific area, rather than spam this
> thread please *start a new thread on one of the relevant w3c lists *(and
> feel free to cc me and Jacob).
>
>  Overall the mood was quite positive and I'm personally optimistic about
> the opportunities here.  Although we identified some substantial
> differences in philosophy, I got the impression we all felt the urgency for
> improving the web platform and recognized that interoperability (and hence
> collaboration) was essential.
>
>  Rick
>
>  [1]
> https://docs.google.com/a/chromium.org/presentation/d/16uP_ofdyXeGXpz4iR1vyi-HDczyAEIH0B3VFI_SxIYY/edit#slide=id.p
> [2]
> https://docs.google.com/a/chromium.org/document/d/1Bfcw9iR1SF2VYCXBegbqhbqWMim-ZEd7_iaQODE-RPY/edit#
>
Received on Wednesday, 20 August 2014 16:56:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:45 UTC