Re: [w3c/gamepad] Add vendorId, productId, name attributes (PR #202)

pedropaulosuzuki left a comment (w3c/gamepad#202)

> > If it only helps when the user is having different type of controllers, I'm not sure how that would be helpful most of the time.
> 
> Do we need to consider whether it's helpful? I agree it's typically not necessary for users to identify a gamepad because usually there's only one connected gamepad, or all the gamepads are the same product model. However, the current API provides a human-facing identifier and application developers sometimes find it useful to present this identifier to users. I think we should assume that a human-facing identifier is helpful to application developers and empower browser implementations to provide the best possible identifier.

Just adding some context as a game developer that also plays games: we often have one controller of each model (one Dualshock 4, one Dualshock 5, one Steam Controller, one Xbox 360 controller, one Xbox Series controller, one Switch Pro controller, and so on) to be able to test all possible controller configurations for our games, and as we have many controllers, having more than one of each model is overkill and generally a waste of money. Thus, for us, it's very common when playing a local co-op game to use different controller models, so I wouldn't say this is as niche as it seems. Also, players sometimes have one Dualshock control for playing Playstation emulated games and one XInput controller for the rest of PC games, and that's also more common that one would think.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/pull/202?email_source=notifications&email_token=ACLYVMIFYWLFHNUDA4NAXGL4WI7JHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRWHEYDANRTGQZ2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOS2XA4S7MNXW23LFNZ2F633QMVXF6Y3MNFRWW#issuecomment-4269006343
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/pull/202/c4269006343@github.com>