Use terminology appropriate for the VR platform in user-facing messages |
|||||||||||
Issue descriptionVR platforms (runtimes/SDKs and maybe even individual devices) use different names for common features. When Chrome needs to reference such a feature, it should use the term that the user of a given platform will be familiar with. The first example of this is the app/menu button. Chrome currently tells the user to, for example, "Press App button to exit" (IDS_PRESS_APP_TO_EXIT). While the "App" button is a concept for Daydream, desktop platforms/devices use different names: * Vive: Menu button (per manual) * Oculus: Menu button (per ovrButton_Enter comment) If this trend holds, we may be able to just use "Menu" on desktop.
,
Oct 11 2017
,
Oct 16 2017
Submitted "App button" to L10n query manager.
,
Jul 4
,
Jul 12
,
Jul 12
,
Jul 16
,
Aug 7
Removing Internals>VR component and remapping to Internals>XR
,
Aug 7
,
Dec 10
,
Dec 13
,
Jan 4
To move forward on this, it seems we should: * have a list the Windows platforms we (currently|intend to) support * document each platform's terminology for core features ** Controller buttons (App/Menu button, track-pad/joystick? others?) * make affordances to expand this list * submit strings for i18n and l10n Am I missing any steps we should take to resolve this issue? Are any of these steps already done/documented? If not, I can create and circulate this doc for review. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by ddorwin@chromium.org
, Oct 11 2017