Background and Problem
I am currently working on a project that consists of 2 browser windows that are being interacted with on 2 separate touch-enabled displays. I am running into the problem that the eventlistener for "touchstart" will not create a new touch event in the same location as a previous one even though these two touches are inside of different windows (ex: (100,100) on each screen, the touch on the second browser window will not be registered at all because there is already one at (100,100) even though it is in a different browser window).
What I've Tested
- I have also confirmed that the touch identifiers for the two touches are different, meaning that the touch events are pooled together somewhere lower and checked before creating a new one.
- Touching in two different locations (ex: 100,100 vs 300,300) will register a touch in each location, therefore the issue is not related to there being one master pointer as I have some complicated master pointer stuff set up that allows multiple master pointers but I will spare you those details.
- There also seems to be a radius around a touch that does not create a new one, even if the second touch is not in the exact same position as the first, the touchstart event is not fired.
My Assumption
It seems to me that when a new touch happens, the touchevent pool is checked and confirms that a new one is able to be made and creates it with identifier of n+1. While this is happening, I assume there is a check somewhere that looks at the positions of all current touches and then doesn't create a new one that is very close to an existing touch.
Expected Function
I am looking for a way to get 2 touchstart events to fire even though they are in the "same" location. Ex: I touch (100,100) with one finger then touch that same spot, I want a touchstart event to fire for each touch