W3C home > Mailing lists > Public > public-webevents@w3.org > April to June 2013

Re: document.createTouch

From: Arthur Barstow <art.barstow@nokia.com>
Date: Mon, 08 Apr 2013 09:31:57 -0400
Message-ID: <5162C6CD.6080000@nokia.com>
To: "ext Kang-Hao (Kenny) Lu" <kanghaol@oupeng.com>
CC: Web Events WG <public-webevents@w3.org>
I think we have reached the point of diminishing terms with Touch Events 
v1 and we have already established the v1 specs' createTouch* functions 
have little to no use `in the wild` (with the possible exception of our 
tests). As such, my preference is to move to Proposed Recommendation 
with the latest [ED] and if/when this bug becomes a serious interop 
problem, we publish errata to address this bug.


[ED] <https://dvcs.w3.org/hg/webevents/raw-file/v1/touchevents.html>

On 4/4/13 5:42 PM, ext Kang-Hao (Kenny) Lu wrote:
> (13/04/05 4:57), Ms2ger wrote:
>> I'd like to point out that Chrome and Gecko (from code inspection, at
>> least) appear to treat all arguments to the document.createTouch method
>> as optional. The spec [1] requires an exception to be thrown when those
>> arguments are omitted, though.
> For this particular function, it also not clear to me what result of the
> following should be:
>    alert(document.createTouch(window, document,
>                               0, 1, 2, 3, 4).clientX);
> Firefox on Android gives 0, while Opera Mobile 12 and Chrome 25 give 1.
> The very short prose:
>    # Creates a Touch object with the specified attributes.
> seems to indicate that Touch has a "view" attribute too, but that
> doesn't seem to be the case.
> Cheers,
> Kenny
Received on Monday, 8 April 2013 13:32:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:09:35 UTC