Troubleshooting
Safari, iPhone and iPad
Safari reads controllers through Apple's Game Controller framework, and so does every browser on an iPhone or iPad, since they're all built on Safari's engine. PadBench works there, within these limits. It needs Safari 17.5 or later.
Which pads it sees
Only the pads Apple supports, such as Xbox, PlayStation and Switch Pro controllers and those made for Apple's devices, less some Safari leaves out. Most arcade sticks and generic pads don't show at all, on a Mac or on an iPhone or iPad, and iPhone and iPad keep a pad's home button for themselves.
What it reads
At most 17 buttons, about 120 times a second, and only while Safari's window is in front: time away from it passes nothing on, and the stage says how long. A press shorter than a reading can be missed, and neither the polling rate nor chatter can be counted. Safari gives no ids, only the pad's name, so PadBench recognises pads there by name alone.
Vibration and lights
Safari has no WebHID, so no lights, trigger effects or motor tones, and no motion, touchpad or battery. A pad vibrates where Safari offers its rumble; where it doesn't, Vibrate is left out of its tools.