The premise of the specification is that using mouse event and touch
events
interchangeably is needed. In reality, nobody was really asking for that
because it is a terrible idea. You can already easily unify pen, touch
and
mouse by writing very little JavaScript, but it is only useful in very
On Tue, Dec 4, 2012 at 10:34 AM, Rick Byers rby...@chromium.org wrote:
The premise of the specification is that using mouse event and touch
events
interchangeably is needed. In reality, nobody was really asking for that
because it is a terrible idea. You can already easily unify pen, touch
On Tue, Dec 4, 2012 at 2:28 PM, Benjamin Poulain benja...@webkit.org wrote:
On Tue, Dec 4, 2012 at 10:34 AM, Rick Byers rby...@chromium.org wrote:
The premise of the specification is that using mouse event and touch
events
interchangeably is needed. In reality, nobody was really asking for
On Nov 28, 2012, at 8:23 AM, Adam Barth aba...@webkit.org wrote:
It looks like this thread got dropped over Thanksgiving. (Responses inline.)
On Thu, Nov 22, 2012 at 1:43 PM, Benjamin Poulain benja...@webkit.org wrote:
On Wed, Nov 21, 2012 at 2:42 PM, Rick Byers rby...@chromium.org wrote:
On Wed, Nov 28, 2012 at 5:53 PM, Benjamin Poulain benja...@webkit.org wrote:
On Wed, Nov 28, 2012 at 8:23 AM, Adam Barth aba...@webkit.org wrote:
I'm sympathetic to these concerns, but, unfortunately, I don't see any
other path that leads to interoperability with Internet Explorer.
Currently,
On Thu, Nov 29, 2012 at 10:27 AM, Adam Barth aba...@webkit.org wrote:
I would prefer WebKit to be wise and wait for either good use cases, or a
better spec.
In my view, the wise course of action is for all user agents to
implement an interoperable set of input events so that authors don't
It looks like this thread got dropped over Thanksgiving. (Responses inline.)
On Thu, Nov 22, 2012 at 1:43 PM, Benjamin Poulain benja...@webkit.org wrote:
On Wed, Nov 21, 2012 at 2:42 PM, Rick Byers rby...@chromium.org wrote:
Outside of the design details, are there any thoughts or concerns
On Wed, Nov 28, 2012 at 8:23 AM, Adam Barth aba...@webkit.org wrote:
I'm sympathetic to these concerns, but, unfortunately, I don't see any
other path that leads to interoperability with Internet Explorer.
Currently, there is little to no content that supports pointer events.
There is also
On Wed, Nov 21, 2012 at 2:42 PM, Rick Byers rby...@chromium.org wrote:
Outside of the design details, are there any thoughts or concerns
about WebKit getting an implementation of pointer events at some
point?
In my opinion, the pointer events spec is a bad idea (at least, in its
current
Hi,
The W3C pointer events working group [1] has put out their first
editors draft of the Pointer Events specification [2]. Pointer events
offer a number of advantages over the current mouse event + touch
event model in WebKit. In particular, having apps state clearly and
declaratively [3]
10 matches
Mail list logo
