This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25214 - Note for pointerType mentions non-existent "appendix" + reinforce best practice of accepting unknown pointer types
Summary: Note for pointerType mentions non-existent "appendix" + reinforce best practi...
Status: RESOLVED FIXED
Alias: None
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Jacob Rossi [MSFT]
QA Contact: Pointer Events Bugzilla list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-31 09:44 UTC by Patrick H. Lauke
Modified: 2014-06-02 22:58 UTC (History)
1 user (show)

See Also:

Attachments

Description Patrick H. Lauke 2014-03-31 09:44:35 UTC 
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.
Comment 1 Patrick H. Lauke 2014-04-01 00:55:09 UTC 
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!");
Comment 2 Patrick H. Lauke 2014-06-01 05:21:55 UTC 
disregard the previous comment, as that is now resolved (and better) by https://www.w3.org/Bugs/Public/show_bug.cgi?id=25220
Comment 3 Jacob Rossi [MSFT] 2014-06-02 22:58:33 UTC 
Fixed as suggested: https://dvcs.w3.org/hg/pointerevents/rev/cf0fa520068d