[prev in list] [next in list] [prev in thread] [next in thread]
List: webkit-dev
Subject: Re: [webkit-dev] pointer events specification - first editors draft
From: Benjamin Poulain <benjamin () webkit ! org>
Date: 2012-11-29 23:02:43
Message-ID: CA+kGwJ=9eTPwekFh3Gj84bMW2A+duS4BHgLL1DwO6jMN_dUHcA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Thu, Nov 29, 2012 at 10:27 AM, Adam Barth <abarth@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
> need to have separate code paths for different user agents. As far as
> I can tell, the only candidate for those events are pointer events. I
> asked you before if you knew of any other paths to interoperability
> and you didn't respond.
>
I did not respond because that has nothing to do with my point. I
wholeheartedly agree interoperability is good.
What I am saying is no support is better than support for a bad ideas.
We have synchronous XHR due to compatibility. If synchronous XHR was
introduced today and I had a chance to prevent it, I would fight for it.
(Of course, that doesn't mean we should slavishly implement whatever
> Microsoft proposes. That's why there's a working group in the W3C: to
> refine and improve the feature's design and specification.)
>
That is all I ask.
Benjamin
[Attachment #5 (text/html)]
On Thu, Nov 29, 2012 at 10:27 AM, Adam Barth <span dir="ltr"><<a \
href="mailto:abarth@webkit.org" target="_blank">abarth@webkit.org</a>></span> \
wrote:<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="im">
> I would prefer WebKit to be wise and wait for either good use cases, or a<br>
> better spec.<br>
<br>
</div>In my view, the wise course of action is for all user agents to<br>
implement an interoperable set of input events so that authors don't<br>
need to have separate code paths for different user agents. As far as<br>
I can tell, the only candidate for those events are pointer events. I<br>
asked you before if you knew of any other paths to interoperability<br>
and you didn't respond.<br></blockquote><div><br></div><div>I did not respond \
because that has nothing to do with my point. I wholeheartedly agree interoperability \
is good.</div><div><br></div><div>What I am saying is no support is better than \
support for a bad ideas.</div> <div>We have synchronous XHR due to compatibility. If \
synchronous XHR was introduced today and I had a chance to prevent it, I would fight \
for it.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">
(Of course, that doesn't mean we should slavishly implement whatever<br>
Microsoft proposes. That's why there's a working group in the W3C: to<br>
refine and improve the feature's design and \
specification.)<br></blockquote><div><br></div><div>That is all I \
ask.</div><div><br></div><div>Benjamin </div></div>
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic