979284 - [Camera] Remove picture/video size selection from settings menu

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::Camera, defect)

Description

[Wilson Page [:wilsonpage]]

For simplicity we are removing the ability for users to select picture/video resolition, and instead selecting the following:

- Largest 4:3 picture size
- Largest 16:9 video size

Comment 1

[Wilson Page [:wilsonpage]]

Landed in dmarcos/camera-dev-rebased

Comment 2

[Diego Marcos [:dmarcos]]

Attachment: pull-request (camera-new-features)

Comment 3

[David Flanagan [:djf]]

Comment on attachment 8385849 [details] [review]
pull-request (camera-new-features)

r- because if I understand correctly, this patch leaves us at the mercy of whatever order the camera driver chooses to list its photo and video size options. 

The initial comment says that this patch selects:

- Largest 4:3 picture size
- Largest 16:9 video size

But actually that only happens if the camera driver lists the largest 4:3 picture size first for both front and back cameras, and the largest 16:9 video size first for both cameras as well.

I'd prefer a patch that explicitly sorted the list of resolutions.  But I'm willing to accept this patch if it comes with a big comment/warning about the assumption being made here.  I'm guessing that Cameracontroller.prototype.onSettingsConfigured is the right place to put such a warning.

Needinfo Wilson since it is his patch but the review request comes from Diego.

Comment 4

[Wilson Page [:wilsonpage]]

Correct, this patch does leave us at the mercy of the order of `camera.capabilities.pictureSizes` if pictureSizes front/back is left unconfigured.

Partners can define supported pictureSizes options, and a `selected` default in js/config/app.js, which allows them to override the default selection logic if they wish. This is exactly the route Madai are taking as they are favouring 16:9 pictureSize as default.

Comment 5

[David Flanagan [:djf]]

Okay. Add a comment, at least, before landing.

Comment 6

[Justin D'Arcangelo [:justindarc]]

This issue has been resolved as part of Bug 980599.