Platform/Features/Camera API: Difference between revisions

m
no edit summary
No edit summary
mNo edit summary
 
(18 intermediate revisions by 6 users 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=Draft
|Feature stage=Design
|Feature status=In progress
|Feature version=Firefox 15  (Maire to confirm)
|Feature health=OK
|Feature health=OK
|Feature status note=This has progress on Mobile where an external app is being used to take a picture, but has no traction on desktop.
|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
|Feature product manager=Chris Blizzard
|Feature product manager=Maire Reavy
|Feature feature manager=Chris Blizzard
|Feature feature manager=Maire Reavy (was Chris Blizzard)
|Feature lead engineer=Fabrice Desré
|Feature lead engineer=Fabrice Desré
|Feature security lead=Ian Melven
|Feature security lead=Ian Melven
|Feature qa lead=Aaron Train
|Feature qa lead=John Hammink
|Feature ux lead=Jennifer Morrow
|Feature additional members=Erin Lancaster (project manager for Android)
}}
}}
{{FeaturePageBody
{{FeaturePageBody
Line 17: Line 21:
* Take a profile photo on facebook, or upload from your gallery.
* Take a profile photo on facebook, or upload from your gallery.
* Instagram for the web.
* Instagram for the web.
|Feature dependencies=* Definition of the experience that we want for developers and users.
|Feature dependencies=* Requires an underlying implementation for capturing from camera devices. (done - anant has volunteered!)
* Requires a solid camera camera API definition for web content.
* Requires an underlying implementation for capturing from camera devices. (done - anant has volunteered!)
* Requires someone to put it all together.
|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 display the image in a canvas for preview and the ability to modify it before uploading it to a server.
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.
|Feature implementation plan=Android support landed:
*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).
https://bugzilla.mozilla.org/show_bug.cgi?id=659188
|Feature ux design=[http://people.mozilla.com/~jboriss/specs/first_spec.png First iteration design specification]
https://bugzilla.mozilla.org/show_bug.cgi?id=621915
|Feature implementation plan=Mobile implementation is almost landed.


Desktop bug, with an implementation for gstreamer (rotted, last touched on 2010-10-18):
Main bug for desktop: [https://bugzilla.mozilla.org/show_bug.cgi?id=692955 Bug 692955]


https://bugzilla.mozilla.org/show_bug.cgi?id=451674
Currently waiting on three things to happen for desktop:


We will use the GIPS code for this feature on desktop.
* Implementation of the Chrome UI (fabrice)
* Implementation of the in-page UI (mounir or dholbert)
* WebRTC integration and landing (jesup):
** Landing Windows build support (ted)
** Pruning code base for image capture (as needed) (jesup)
** Legal review (under way, no problems expected)
** Security review of code paths needed for image capture (jesup, curtis)
** Picking a 'stable point' in WebRTC upstream to use as the mergepoint (jesup)
** Landing review of the capture code from webrtc (jesup)
** Post-landing testing and debugging (jesup, fabrice, qa, etc)
 
Ignore stuff below this line, here for history only.
 
Android support landed:
* https://bugzilla.mozilla.org/show_bug.cgi?id=659188
* 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).
}}
}}
{{FeatureInfo
{{FeatureInfo
Line 42: Line 59:
|Feature engineering team=DOM
|Feature engineering team=DOM
}}
}}
{{FeatureTeamStatus}}
{{FeatureTeamStatus
|Feature security status=sec-review-unnecessary
|Feature security notes=Per note from imelven review unnecessary
}}
Confirmed users, Bureaucrats and Sysops emeriti
2,974

edits