document.createTouch/document.createTouchList are useless without new TouchEvent() or event.initTouchEvent()

Hello Web Events WG folks,

I am new to this spec and I haven't been really following the
development of it. I bet this has been debated and I don't feel like
explaining too much about this (spec modularity and such), so I'll just
list some options:

A. no change - the spec is fine as it is.
B. add a note in Section 6 Extensions to the Document Interface in this
vein:

  # createTouch() and crateTouchList() cannot be used directly in any
  # of the methods defined in this version of Touch Events, but it
  # might be used in a future version or a proprietary extension of
  # this API. Also, the existence of these functions can be used for
  # feature detection.

I don't know if it is appropriate to mention event.initTouchEvent here.

C. remove Section 6 Extensions to the Document Interface and relevant
tests - this has the benefits of giving browsers the chance to remove
document.createTouch/document.createTouchList along with
event.initTouchEvent() in the future.
D. acknowledge that browsers are not going to remove
event.initTouchEvent() in the future and spec it in this version.
E. add new TouchEvent() (and perhaps new Touch()/TouchLis()t to replace
document.createTouch/document.createTouchList)
F. other variants such as making
document.createTouch/document.createTouchList true under ToBoolean() the
only requirement.


I am less optimistic about removing anything from WebKit so my
preference would be

  D > C > E > B >>>> F > A (which is really confusing. How are readers
of this spec supposed to know what
document.createTouch/document.createTouchList are for?)

I found this discussion two years ago[1], but it was under the assumption

[[
  (As context for anyone new to the working group, our goal is for
  Touch Events v1 to include only those features that have multiple
  interoperable implementations today.  Any features that don't meet
  that criterion today will go into the v2 spec.)
]]

, which doesn't seem to hold so people might have a different opinion now.

[1]
http://lists.w3.org/Archives/Public/public-webevents/2011JulSep/thread#msg53



Cheers,
Kenny
-- 
Web Specialist, Opera Sphinx Game Force, Oupeng Browser, Beijing
Try Oupeng: http://www.oupeng.com/

Received on Monday, 25 March 2013 15:10:52 UTC