RE: [Bug 20107] New: Pointer events should indicate stylus eraser/inversion

Here are some suggested changes to resolve issue 20107.

Add a new set of button and buttons properties to section [1] to accommodate ‘pen contact with eraser button pressed’.

 state = pen contact with eraser button pressed
 button = 5
 buttons = 32

For supporting new buttons in the future, new values for button and button properties can be assigned by following the conventions outlined in MouseEvent.button [2] and MouseEvent.buttons [3] properties.  

-----Original Message-----
From: [] 
Sent: Tuesday, November 27, 2012 4:58 PM
Subject: [Bug 20107] New: Pointer events should indicate stylus eraser/inversion

            Bug ID: 20107
           Summary: Pointer events should indicate stylus eraser/inversion
    Classification: Unclassified
           Product: PointerEventsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Pointer Events specification
        QA Contact:

Opened on behalf of Brandon Wallace:

From: Jacob Rossi <>
Date: Fri, 28 Sep 2012 18:50:30 +0000
To: Brandon Wallace <>, ""

From: Brandon Wallace <>
Date: Wed, 26 Sep 2012 09:44:27 -0700 (PDT)
Message-ID: <>
To: "" <>
> The spec does not seem to include any way to determine when the stylus eraser is generating events.  Or even if the stylus is being used while inverted.  Would these events show up with additional pointerType values?  Or would there be additional properties on the pointer event to express this state?
> Brandon

I think it'd be exposed through the button/buttons properties (see my other mail).  It's still a pen stylus, but a different button (tip is the primary, barrel is the secondary, second barrel might be the "middle" button, not sure yet what the best value for eraser is though). IE10 just supports the tip and barrel button. 

DOM3 Events set up a pattern for assigning values to additional mouse buttons.
We might want to do the same in this spec. We define the most common modifiers on devices today, and define a convention for assigning additional values in the future.


You are receiving this mail because:
You are on the CC list for the bug.

Received on Tuesday, 18 December 2012 05:29:34 UTC