- From: <bugzilla@jessica.w3.org>
- Date: Mon, 31 Mar 2014 09:44:35 +0000
- To: public-pointer-events-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25214 Bug ID: 25214 Summary: Note for pointerType mentions non-existent "appendix" + reinforce best practice of accepting unknown pointer types Product: PointerEventsWG Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: Pointer Events specification Assignee: jrossi@microsoft.com Reporter: redux@splintered.co.uk QA Contact: public-pointer-events-bugzilla@w3.org CC: public-pointer-events@w3.org 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. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 31 March 2014 09:44:37 UTC