Camera API not working via the html Input type=file accept=image/*
Categories
(Firefox for Android Graveyard :: Audio/Video, defect, P2)
Tracking
(geckoview66 affected, firefox-esr68 unaffected, firefox67 unaffected, firefox67.0.1 unaffected, firefox68 unaffected, firefox69 disabled)
| Tracking | Status | |
|---|---|---|
| geckoview66 | --- | affected |
| firefox-esr68 | --- | unaffected |
| firefox67 | --- | unaffected |
| firefox67.0.1 | --- | unaffected |
| firefox68 | --- | unaffected |
| firefox69 | --- | disabled |
People
(Reporter: dmanter, Assigned: petru, NeedInfo)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
Steps to reproduce:
http://robnyman.github.io/camera-api/
Camera Snap Shot not loaded to web page after the picture is taken.
Specifically the OK button to accept the image doesn't appear.
Android v9 on Samsung S8 not working. On same phone, same link above works in Chrome. We have a web site that uses same code with camera API with same results.
Actual results:
The Camera comes up and allows you to snap a picture but the camera window doesn's then have the OK button to accept the image and close the camera window.
However in CHrome, after picture is taken, the camera window present and accept/ok button to accept the picture and close the camera window and then the image appears on the web page.
Expected results:
It should allow the Camera window to have the Accpet/ok button to accept the snap shot.
FireFox 66.0.5 was just installed today on the Samsung S8
Comment 1•6 years ago
|
||
This works as intended on Nightly, but does not work on 66.0.5.
| Assignee | ||
Comment 2•6 years ago
|
||
This sounds like bug 1507531.
| Assignee | ||
Comment 3•6 years ago
|
||
I investigated this with the help of Stefan today and we could not reproduce the issue on
- a Samsung S7 with Android 8
- a Samsung S8 with Android 9
- a Samsung S9 with Android 9
A logcat would help.
I see Paul confirmed that the issue is not reproducing in Nightly.
The issue is also not reproducing for us on Firefox Beta 67.
With Firefox 67 being planned for release in the next few days can you please try the latest Firefox Beta or Firefox 67 release to see if the issue is still reproducing for you?
Updated•6 years ago
|
Comment 4•6 years ago
|
||
esr68=unaffected because 68=unaffected
Updated•5 years ago
|
Description
•