Constraints for image capture are well supported according to the standard.
Can you try {advanced: {torch: {exact: true}}} ?

exact: true does not seem to work at all.

Sorry, I made a mistake in the initial report, it should be {advanced: [{ torch: true }]} instead of {advanced: { torch: true }} (and for the rest)

Looking at the code, it looks like the original example should work too.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

@dillon: Could you please respond to comment#3, Does the original example work?

@chelamcherla, unfortunately it did not :/

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

dillon@ thanks for the codepen and the report. Just tried with my 
sailfish 9 (PQ1A) and Chrome 71.0.3578.98 (Stable) and turning the
torch on and off works for me :-?

Could you provide details about the concrete models you have tried
where it works and doesn't work please? Also the Android and Chrome
versions would be useful for triaging.

Assigning to chfremer@ for further triaging as well.

@mcasas

Tried again on my android 5.1 XT1039 (moto g) in chrome 71.0.3578.83. I don't have access to other android devices to test :(

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.