25214 2014-03-31 09:44:35 +0000 Note for pointerType mentions non-existent "appendix" + reinforce best practice of accepting unknown pointer types 2014-06-02 22:58:33 +0000 1 1 1 Unclassified PointerEventsWG Pointer Events specification unspecified PC Windows NT RESOLVED FIXED https://www.w3.org/Bugs/Public/show_bug.cgi?id=25220 P2 normal --- 1 redux jrossi public-pointer-events public-pointer-events-bugzilla oldest_to_newest 103159 0 redux 2014-03-31 09:44:35 +0000 Currently, the note in 5.1 PointerEvent Interface > pointerType definition reads: NOTE See the examples in the appendix for sample code. the link jumps to earlier in the document (3. Examples). So, not really an appendix (which is generally at the end, and called that). The note is also a bit wishy-washy...I'm guessing we want to draw attention to example 2 which shows how pointerType can be used to determine what kind of input we're dealing with. Suggest changing to just: NOTE See example 2 for a basic demonstration of how the <code>pointerType</code> can be used. Also note that developers should include some form of default handling to cover user agents that may have implemented their own custom <code>pointerType</code> values and for situations where <code>pointerType</code> is simply an empty string. 103213 1 redux 2014-04-01 00:55:09 +0000 Possibly, in concert with this, may be worth adding a comment to the code in example 2 default: alert("Not sure what device was used!"); to reinforce it once more? default: /* pointerType empty string or UA-specific custom type */ alert("Not sure what device was used!"); 107093 2 redux 2014-06-01 05:21:55 +0000 disregard the previous comment, as that is now resolved (and better) by https://www.w3.org/Bugs/Public/show_bug.cgi?id=25220 107163 3 jrossi 2014-06-02 22:58:33 +0000 Fixed as suggested: https://dvcs.w3.org/hg/pointerevents/rev/cf0fa520068d