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 20219 - Make pointerType a string instead of an enum?
Summary: Make pointerType a string instead of an enum?
Status: RESOLVED FIXED
Alias: None
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Jacob Rossi [MSFT]
QA Contact: This bug has no owner yet - up for the taking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-03 22:22 UTC by Rick Byers
Modified: 2012-12-14 21:19 UTC (History)
1 user (show)

See Also:

Attachments

Description Rick Byers 2012-12-03 22:22:13 UTC 
The current draft spec has this for pointerType:

ISSUE 2
Should this be a string rather than enumerated constants? What about extensibility?

We need to resolve this.  In particular, for scenarios like bug 20218 (where you could imagine different vendors adding different extensions, and certainly want websites to be able to opt-in to understanding new types of pointers) I think a string is preferable to an enum.  Also a string seems more consistent with the DOM event model.
Comment 1 Jacob Rossi [MSFT] 2012-12-14 21:19:58 UTC 
Per 12/11 telecon resolution, making change that pointerType will be a DOMString. Normative values are provided for mouse, pen, and touch input. An enum is not used in order to facilitate synthetic events (e.g. from future polyfills) providing arbitrary values.

RESOLUTION: http://www.w3.org/2012/12/11-pointerevents-minutes.html