Closed
Bug 905506
Opened 11 years ago
Closed 11 years ago
[Buri][TOR][MMS]This is not necessarily to crop the picture before going to MMS
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect, P2)
Firefox OS Graveyard
Gaia::SMS
Tracking
(blocking-b2g:-)
RESOLVED
WONTFIX
blocking-b2g | - |
People
(Reporter: sync-1, Unassigned)
References
Details
Attachments
(1 file)
226.66 KB,
image/x-png
|
Details |
AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.184
Firefox os v1.1
Mozilla build ID:20130806071254
DEFECT DESCRIPTION:
This is not necessarily to crop the picture before going to MMS
REPRODUCING PROCEDURES:
1.Launch message app
2.Tap attachment icon,select gallery
3.It enter the UI to Crop the picture->KO
EXPECTED BEHAVIOUR:
This is not necessarily self explanatory and should be considered changed. Or some explanation should be added somehow.
ASSOCIATE SPECIFICATION:
TEST PLAN REFERENCE:
TOOLS AND PLATFORMS USED:
USER IMPACT:
Mid
REPRODUCING RATE:
5/5
For FT PR, Please list reference mobile's behavior:
Updated•11 years ago
|
Summary: [Buri][MMS]This is not necessarily to crop the picture before going to MMS → [Buri][TOR][MMS]This is not necessarily to crop the picture before going to MMS
Comment 3•11 years ago
|
||
We can see in gallery activity for "pick" has a default "crop". Is this a spec for FF OS?
Comment 4•11 years ago
|
||
In the "Crop" iframe, On top in the right side there is a checkbox already checked.
This is not explanatory, user don't know what he has to do.
EXPECTED BEHAVIOUR:
Provide a explanatory menu. May be checkbox should be unchecked first, then end
user will has to check it to validate after cropped picture.
Comment 5•11 years ago
|
||
QA - what is the current flow?
Can the user go 'back' from the crop screen to continue sending the MMS? What happens with the box checked or unchecked? It may not be the clearest workflow but it's also too late to add 'explanatory menu'. If checkbox check/uncheck works with back button taking you to continue sending the message I think we're fine to not block here.
Keywords: qawanted
In response to Comment 5
Tested on Leo Moz Ril
Environmental Variables
Build ID: 20130816041203
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/09a8c5b6b287
Gaia: 6040508a535b587d4155356a47b22d7bd9ea4de7
Platform Version: 18.1
Going back from the Crop screen would just take the user back to the Gallery to select another picture and clicking back again from gallery page would take the user back to the message without any picture attached.
There is no unchecking process on the crop screen after tapping the “checked box” icon on right corner of the crop screen page the edited/not edited picture gets attached to the message and the user is taken back to the page where the user can send the message successfully upon tapping the send button.
Flow: Message app>Tap on pin icon>select gallery>select a picture>tap on checked box on upper right corner>Type in the name /number in the “To” field on the message page >click send
Comment 7•11 years ago
|
||
likely by design. need UX confirmation
Flags: needinfo?(firefoxos-ux-bugzilla)
Comment 8•11 years ago
|
||
Flagging Jacqueline since Gallery is in her wheelhouse this week. I don't think this is a blocker, but we should clarify the expected behavior.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(jsavory)
Updated•11 years ago
|
blocking-b2g: leo? → -
Comment 9•11 years ago
|
||
Is this feature(crop) coming from your specifcation?
Cropping for sure exist, when the picture is selected as wallpaper on some of
the android phones.
So, please confirm, why need crop in this place?
Thanks!
Comment 10•11 years ago
|
||
The crop feature allows users to send portions of a photo instead of requiring them to always send the entire photo. Removing it would not enhance the experience and I recommend we keep this feature.
Regarding the checkbox in comment 6, the icon has been replaced with the "Done" button.
Flags: needinfo?(jsavory)
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Comment 11•11 years ago
|
||
closing WONTFIX as there seems to be a consensus in the UX team that this won't be changed. Please reopen if needed.
You need to log in
before you can comment on or make changes to this bug.
Description
•