[Feature Request] facingMode constraint is essential for this library to work

Very nice and clean module but… is useless without facingMode constraint, device label can be in any language making the camera choice impossible

Example:

{id: "AFB981283186FBA62F2947AA63940A4482BF80C3", label: "Πίσω κάμερα"}

Alternative, selecting between 4 options (devices), where only one option is essential its not the best user experience

[mebjas]

I can possibly exposure arguments to getCameras so you can request camera of choice and build your user interface on top of it.

You can call it like

Html5Qrcode.getCameras({ facingMode: "user" })
  .then(devices => {
    // handle the returned devices
});

or

Html5Qrcode.getCameras({ facingMode: { exact: "environment" } })
  .then(devices => {
    // handle the returned devices
});

Similar to video part of web api syntax - https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia

@dennmtr WDYT?

[max2ti]

@mebjas

I’ve done some more tests and found that the problem appears only if the div used by html5qrcode is managed by Vue.js. I’ve swapped the call to Html5Qrcode#getCameras() with a call to a generic awaitable (an async/await wrapper of setTimeout) and it worked, so it’s not what Html5Qrcode#getCameras() does, any “time waster” works.

There’s probably nothing wrong with html5-qrcode, I must be doing something wrong with Vue (I’m integrating html5-qrcode in a big pre-existing vue app).

EDIT: I was calling Html5Qrcode#getCameras() before the component was fully mounted, moved it to the mounted event, now it works as expected. Sorry for having wasted some of your time.