Platform/Features/Camera API: Difference between revisions

m
no edit summary
No edit summary
mNo edit summary
 
(7 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{FeatureStatus
{{FeatureStatus
|Feature name=Ability to take a picture from a web page (<input type="picture">)
|Feature name=Ability to take a picture from a web page (<input type="picture">) - "Phase 1"
|Feature stage=Design
|Feature stage=Design
|Feature status=In progress
|Feature status=In progress
|Feature version=Firefox 14 (Maire to confirm)
|Feature version=Firefox 15  (Maire to confirm)
|Feature health=OK
|Feature health=OK
|Feature status note=This is almost completed on Mobile where driver support is available via an external app; support for desktop will be added after the base WebRTC code is landed.  
|Feature status note=This is almost completed on Mobile where driver support is available via an external app; support for desktop will be added after the base WebRTC code is landed.
}}
}}
{{FeatureTeam
{{FeatureTeam
Line 22: Line 22:
* Instagram for the web.
* Instagram for the web.
|Feature dependencies=* Requires an underlying implementation for capturing from camera devices. (done - anant has volunteered!)
|Feature dependencies=* Requires an underlying implementation for capturing from camera devices. (done - anant has volunteered!)
|Feature requirements=For mobile we should use an external app for performance reasons.
|Feature requirements=For mobile we should use an external app for performance reasons.


For desktop we should be able to take an image snapshot.
For desktop we should be able to take an image snapshot.
|Feature non-goals=* This does not include the ability to capture a video and send that video somewhere.  This is only for taking a picture.
|Feature non-goals=* This does not include the ability to capture a video and send that video somewhere.  This is only for taking a picture.
*Previewing the image in a canvas with the ability to modify it before uploading it to a server won't be possible with this implementation.
*Previewing the image in a canvas with the ability to modify it before uploading it to a server;  previewing and modifying the image won't be possible with this implementation ([https://wiki.mozilla.org/Camera_API_-_Phase_2_%28getUserMedia%29 Phase 2 ] will eventually provide that functionality).
|Feature ux design=[http://people.mozilla.com/~jboriss/specs/first_spec.png First iteration design specification]
|Feature ux design=[http://people.mozilla.com/~jboriss/specs/first_spec.png First iteration design specification]
|Feature implementation plan=Main bug:
|Feature implementation plan=Mobile implementation is almost landed.


https://bugzilla.mozilla.org/show_bug.cgi?id=692955
Main bug for desktop: [https://bugzilla.mozilla.org/show_bug.cgi?id=692955 Bug 692955]


Currently waiting on three things to happen:
Currently waiting on three things to happen for desktop:


* Implementation of the Chrome UI (fabrice)
* Implementation of the Chrome UI (fabrice)  
* Implementation of the in-page UI (mounir or dholbert)
* Implementation of the in-page UI (mounir or dholbert)
* WebRTC integration and landing (jesup et al):
* WebRTC integration and landing (jesup):
** Fixing of the Windows build issues (ted)
** Landing Windows build support (ted)
*** Build servers will need to be updated to include additional Win32 SDK files (release eng)
** Pruning code base for image capture (as needed) (jesup)
** Pruning code base for image capture (as needed) (jesup)
** Update to live in shared lib with other media modules (jesup and/or ted)
** Legal review (under way, no problems expected)
** Legal review (under way, no problems expected)
** Security review of code paths needed for image capture (jesup, curtis)
** Security review of code paths needed for image capture (jesup, curtis)
** Picking a 'stable point' in WebRTC upstream to use as the mergepoint (jesup)<br>The drop used for upcoming Chrome integration would probably be a good choice.
** Picking a 'stable point' in WebRTC upstream to use as the mergepoint (jesup)
** Landing review of the capture code from webrtc (jesup)
** Landing review of the capture code from webrtc (jesup)
** Post-landing testing and debugging (jesup, fabrice, qa, etc)
** Post-landing testing and debugging (jesup, fabrice, qa, etc)
Line 51: Line 48:


Android support landed:
Android support landed:
https://bugzilla.mozilla.org/show_bug.cgi?id=659188
* https://bugzilla.mozilla.org/show_bug.cgi?id=659188
https://bugzilla.mozilla.org/show_bug.cgi?id=621915
* https://bugzilla.mozilla.org/show_bug.cgi?id=621915
 
|Feature landing criteria=Remaining bug for Android: [https://bugzilla.mozilla.org/show_bug.cgi?id=708175 Bug 708175], which was just marked resolved fixed (April 14).
Work is going on in this bug:
 
https://bugzilla.mozilla.org/show_bug.cgi?id=692955
 
We will use the GIPS code for this feature on desktop.
}}
}}
{{FeatureInfo
{{FeatureInfo
Confirmed users, Bureaucrats and Sysops emeriti
2,974

edits