{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/mediacapture-depth/issues/100","repository_url":"https://api.github.com/repos/w3c/mediacapture-depth","labels_url":"https://api.github.com/repos/w3c/mediacapture-depth/issues/100/labels{/name}","comments_url":"https://api.github.com/repos/w3c/mediacapture-depth/issues/100/comments","events_url":"https://api.github.com/repos/w3c/mediacapture-depth/issues/100/events","html_url":"https://github.com/w3c/mediacapture-depth/issues/100","id":139292548,"number":100,"title":"Setting unit in constraints","user":{"login":"dontcallmedom","id":216410,"avatar_url":"https://avatars.githubusercontent.com/u/216410?v=3","gravatar_id":"","url":"https://api.github.com/users/dontcallmedom","html_url":"https://github.com/dontcallmedom","followers_url":"https://api.github.com/users/dontcallmedom/followers","following_url":"https://api.github.com/users/dontcallmedom/following{/other_user}","gists_url":"https://api.github.com/users/dontcallmedom/gists{/gist_id}","starred_url":"https://api.github.com/users/dontcallmedom/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dontcallmedom/subscriptions","organizations_url":"https://api.github.com/users/dontcallmedom/orgs","repos_url":"https://api.github.com/users/dontcallmedom/repos","events_url":"https://api.github.com/users/dontcallmedom/events{/privacy}","received_events_url":"https://api.github.com/users/dontcallmedom/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-08T14:34:48Z","updated_at":"2016-03-10T04:13:25Z","closed_at":null,"body":"The way constraints for mediastreamtrack have been defined is to allow browser-mediated negotiations of allowable ranges in which an application can operate on the said track.\r\n\r\nUsing this to indicate the unit of the reported values seems a poor application of that concept, since there is no particular reason why one would negotiate between meters and milimeters (or at least, I can't see what reason); in general, I'm not sure there is any value in saving the developers from a division or multiplication by a fixed number (1000) here."},"comment":{"url":"https://api.github.com/repos/w3c/mediacapture-depth/issues/comments/194654560","html_url":"https://github.com/w3c/mediacapture-depth/issues/100#issuecomment-194654560","issue_url":"https://api.github.com/repos/w3c/mediacapture-depth/issues/100","id":194654560,"user":{"login":"huningxin","id":1005673,"avatar_url":"https://avatars.githubusercontent.com/u/1005673?v=3","gravatar_id":"","url":"https://api.github.com/users/huningxin","html_url":"https://github.com/huningxin","followers_url":"https://api.github.com/users/huningxin/followers","following_url":"https://api.github.com/users/huningxin/following{/other_user}","gists_url":"https://api.github.com/users/huningxin/gists{/gist_id}","starred_url":"https://api.github.com/users/huningxin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/huningxin/subscriptions","organizations_url":"https://api.github.com/users/huningxin/orgs","repos_url":"https://api.github.com/users/huningxin/repos","events_url":"https://api.github.com/users/huningxin/events{/privacy}","received_events_url":"https://api.github.com/users/huningxin/received_events","type":"User","site_admin":false},"created_at":"2016-03-10T04:13:25Z","updated_at":"2016-03-10T04:13:25Z","body":"@dontcallmedom , thanks for opening this issue!\r\n\r\nFrom what I know, some depth cameras allow to set depth value unit. It allows applications to configure the depth camera precision and accuracy.\r\n\r\nAs it is device specific currently, I am fine to remove it from constraints. But it still makes sense to keep it in settings. WDYT? @dontcallmedom @anssiko "}}