Handling both desktop and touch devices, js app code will often fork the libraries loaded in and behavior wired up depending on if touch events are detected.
The most common detect for this is: 'ontouchstart' in window
The Emulate Touch Events feature in the Inspector will create touch events, but any code relying on a feature detect will fork in the wrong path.
Could the feature also expose touch events like the above in the DOM so the page can fork behavior correctly?