Nope, it does not generate touch events. I tried in Firefox, Chrome and Safari. It's always just generating mouse and pointer events, no touch events. If you use the chrome developer tools and click the 2nd button on the top right ("Toggle Device Toolbar") then it generates touch events. But it's only the same as with mouse, it doesn't generate multiple touch points. So, in short: Nope, it's just a regular mouse to the browser.

Had a similar issue when cross building from an intel mac to an M1 mac target. My issue was that I specified xcodebuild archive -project 'path/to/my/proj.xcodeproj' -destination 'platform=macOS,arch=armv8' But to use a "build" and not a "build and run" target the destionation needs to be prepended with generic/ So in my case it would be something like xcodebuild archive -project 'path/to/my/proj.xcodeproj' -destination 'generic/platform=macOS,arch=armv8' Or if you have multiple architectures specified in your project already probably just xcodebuild archive -project 'path/to/my/proj.xcodeproj' -destination 'generic/platform=macOS'

In case anyone else lands here via Google. The slowdown I've seen is most severe when WebGL 2.0 is enabled. So if you are in developer mode in Safari you can go to "Develop" -> "Experimental Features" -> untick "WebGL 2.0". This will significantly improve performance if the page you're trying to view also supports webgl 1.0 (as the demo page posted by Bersaelor does). Still nowhere near Firefox or Chome performance, but still a 20x improvement in frametime for me in Safari comparing with and and without WebGL 2.0 enabled.