1020004 - [B2G][Tarako][Facebook] An image sent in messages or chat will extend beyond the user's field of vision

Status: RESOLVED FIXED

(Tech Evangelism Graveyard :: Preinstalled B2G Apps, defect, P2)

Description

[Rachel Pribble [:rpribble]]

Attachment: Screenshot.png

Description:
If the user sends an image through the messaging feature or chat, the image will be too large and will not be resized to fit the screen.

Repro Steps:
1) Update device to BuildID: 20140602014001
2) Install and launch Facebook from the marketplace
3) Tap on messages icon or chat
4) Send an image from the gallery to a friend

Actual:
Images appear too large for frame.

Expected:
USer is able to see entire image.

Environmental Variables:
Device: Tarako 1.3T
BuildID: 20140602014001
Gaia: 335486c42498fa7a93c21e4d6121199728602ab8
Gecko: 55e4d83019e5
Version: 28.1
Firmware Version: SP6821a-Gonk-4.0-4-29

Notes: 

Repro frequency: 100%
See attached: Screenshot, logcat

Comment 1

[Rachel Pribble [:rpribble]]

Qwanted for results on Buri v1.3 or will post myself in the morning.

Comment 2

[Rachel Pribble [:rpribble]]

This issue also occurs on the Buri v1.3 MOZ ril.

Environmental Variables:
Device: Buri v1.3 MOZ ril
BuildID: 20140529024024
Gaia: 5bd226b03a2d63dfe9df204f7c0afb9984e8fd42
Gecko: 42ef074f380f
Version: 28.0
Firmware Version: v1.2-device.cfg

Image will display outside too large outside the user's field of vision.

Note: If the user exits the message feature then returns to the message thread, the image will display resized properly on both Tarako and Buri.

Comment 3

[Nicole Fong]

Please review and provide estimated fix date.  Thank you!

Comment 4

[joseenrique.alvarezfernandez]

I've tested this on ZTE OPEN C v1.3 and Flame v2.0 and seems to be solved. Could anyone else test this bug to confirm that is no longer a bug and close it

Comment 5

[Michael Ellis]

Attachment: fb pic in chat.png

Comment 6

[Michael Ellis]

Thanks for reporting this fix, Jose.  Confirmed as fixed on my end as well on reference device.

Closing this bug as resolved.  Photo of current UX attached