Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expose debugging values #250

Open
jsantell opened this issue Jun 1, 2017 · 1 comment
Open

Expose debugging values #250

jsantell opened this issue Jun 1, 2017 · 1 comment
Labels
enhancement

Comments

@jsantell
Copy link
Contributor

jsantell commented Jun 1, 2017

We should expose values like the build version number, as well as what dpdb values are being used easily from WebVRPolyfill for debugging
jsantell added a commit that referenced this issue Jun 1, 2017
@jsantell
Expose build version on WebVRPolyfill.version, for #250
1eecafa
@cvan
Copy link
Contributor

cvan commented Jun 9, 2017

This is a good idea. Thoughts on how the debug mode would be enabled/toggled? A key set on window.WebVRConfig (or, if/when the exposed module interface changes, in the settings object passed when initialising the Polyfill)? A value set via localStorage? A query-string parameter or hash in the URL?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cvan @jsantell