Closed Bug 873028 Opened 11 years ago Closed 11 years ago

[MMS] Compose and Reply a message. Implement MMS indicator

Categories

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

x86
macOS
defect
Not set
normal

Tracking

(blocking-b2g:leo+, b2g18 fixed)

RESOLVED FIXED
blocking-b2g leo+
Tracking Status
b2g18 --- fixed

People

(Reporter: vicky, Assigned: gnarf)

References

Details

Attachments

(5 files, 12 obsolete files)

38.48 KB, image/png
Details
35.71 KB, image/png
Details
37.72 KB, image/png
Details
12.03 KB, image/png
Details
4.13 KB, text/plain
borjasalguero
: review+
Details
Implement MMS indicator in messages list as shown in the attachment. The size and color of the font is specified there as well.
Blocks: 872514
Fixed a bug whic
Assignee: nobody → gnarf37
blocking-b2g: --- → leo?
Attached patch patch v1 (obsolete) — Splinter Review
Pinging two reviewers, whoever gets here first, please remove the other flag.

This fixed a bug where an image being attached to a message wouldn't cause the MMS indicator to show up.

Also, applies styles to look like the visual mock
Attachment #753397 - Flags: review?(felash)
Attachment #753397 - Flags: review?(fbsc)
Attached image Screenshot with patch (obsolete) —
Attached image Screenshot with patch (obsolete) —
Attachment #753399 - Attachment is obsolete: true
Comment on attachment 753397 [details] [diff] [review]
patch v1

Review of attachment 753397 [details] [diff] [review]:
-----------------------------------------------------------------

I see the following problem:
* the counter is not properly placed when it's displayed very soon (eg: try to type a SMS with a character "ê")

see screenshot (don't look at the overing problems due to the fact that I have a big send button, this is bug 871986)

::: apps/sms/style/sms.css
@@ +559,5 @@
>    padding-right: 0.5rem;
>  }
>  
>  [data-message-type="mms"] #messages-send-button.has-counter:before {
>    content: 'MMS';

don't we need a display:block ? otherwise I suspect the padding-left won't apply ?
(but I'm not so sure)
Attachment #753397 - Flags: review?(felash)
Attachment #753397 - Flags: review?(fbsc)
So this bug with the counter showing up early was one I discussed with borja at the work week.  The fact that the counter might show up before the input was tall enough to hold it was not considered possible. Darn long chars. 

Borja/Julien - Can you look at the CSS with this in mind and suggest the proper code to use, or can someone else take my patch and fix the CSS correctly? I had another positioning model setup at one point that dealt with this scenario, but it wasn't considered possible :)
Flags: needinfo?(felash)
Flags: needinfo?(fbsc)
as discussed on IRC, will try to find the right CSS tomorrow.
Assignee: gnarf37 → felash
Flags: needinfo?(felash)
blocking-b2g: leo? → leo+
So, I checked 1.0.1, and I really like how the SMS counter is just above the send button.

Victoria, could it be possible to have the SMS character counter like in 1.0.1, which would prevent having the problem I highlight in comment 6 ? We still can put the MMS indicator where you want it to be.

To reproduce easily the comment 6 problem, start a SMS with "Ê" and then add lots of short characters like "l" or "i", the counter will appear before the end of the second line.
Assignee: felash → gnarf37
Flags: needinfo?(vpg)
(Gave it back to :gnarf because if this simpler solution is agreed by Victoria, he'll be able to move forward)
Attached image No issue with height in English (obsolete) —
Flags: needinfo?(fbsc)
I've seen that there is no issue of the height neither master or v1-train. Corey, this patch is ready for review?
Flags: needinfo?(gnarf37)
I've just checked the issue with characters as 'ë' etc... Waiting Vicky!
Hi, so if there's really a problem, please use this layout I am attaching, is the MMS indicator without the vertical line in the left and separated from the send button by a 0.6 rem vertical space. Please make sure you update the counter like this also.
Flags: needinfo?(vpg)
Attached image screenshot of error with new design spec (obsolete) —
This has the changes from victoria, but still causes a problem
Attachment #753421 - Attachment is obsolete: true
Flags: needinfo?(gnarf37) → needinfo?(vpg)
I see Corey, thanks for the screenshot. This is no longer a strict visual matter, so pingin Ayman to see if he can give some input here.
Flags: needinfo?(vpg) → needinfo?(aymanmaat)
Attached file patch v2 (obsolete) —
sets a bunch of absolute positioning to put the counter right above the send button
Attachment #753397 - Attachment is obsolete: true
Attachment #756025 - Flags: review?(fbsc)
Attached image screenshot with patch - mms (obsolete) —
latest patch
Attachment #753400 - Attachment is obsolete: true
Attached image Screenshot with patch - short text (obsolete) —
Corey, those screenshots are not a valid solution. Will wait for Ayman's input to see if there's a different placement solution for it.
Attachment #755987 - Attachment is obsolete: true
Comment on attachment 755989 [details]
No issue with height in French

obsoleted borja's screenshots since he wasn't using a ë type character to make the segment length shorter.
Attachment #755989 - Attachment is obsolete: true
kicking the bug over to borja - I think borja can take my patch and fix the CSS with input from victoria - the code shouldn't need to change at all.
Assignee: gnarf37 → fbsc
Attached file Pull Request (obsolete) —
Attachment #756025 - Attachment is obsolete: true
Attachment #756025 - Flags: review?(fbsc)
Attachment #757358 - Flags: review?(gnarf37)
I've created this path for fixing the functionality (now it's broken), and it's agreed with UX. Furthermore we are going to add the right styles here https://bugzilla.mozilla.org/show_bug.cgi?id=878758 as a followup.
I'm a little confused here --- This doesn't include the code/unit test fixes from my patch?  Why do we need the followup?  Sounds like your pull is the followup and my old patch is this bug?  I was assuming you would just take my patch and fix the CSS on top of it?
Hi Corey,
Feel free to take this code and use this CSS in your patch. After talking with UX we are going to fix the issue (because now it's broken), and we are going to work in the followup with UX for creating a better solution aligned with all the requirements (that's why the followup).
Okay! Thanks - I'm going to take my code, + your css, and r=you and just land it then?
Assignee: fbsc → gnarf37
Merge both codes and I will simply test it and r ok? Thanks!
Attachment #756026 - Attachment is obsolete: true
Attachment #756027 - Attachment is obsolete: true
Attached file patch v3
Here is an updated patch Borja - Please check it out
Attachment #756019 - Attachment is obsolete: true
Attachment #757358 - Attachment is obsolete: true
Attachment #757360 - Attachment is obsolete: true
Attachment #757358 - Flags: review?(gnarf37)
Attachment #757981 - Flags: review?(fbsc)
Attachment #757981 - Flags: review?(fbsc) → review+
master: https://github.com/mozilla-b2g/gaia/commit/64ab5d6649a3227a98c5808d3eaa8910d571d3a1
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(aymanmaat)
Resolution: --- → FIXED
Uplifted 64ab5d6649a3227a98c5808d3eaa8910d571d3a1 to:
v1-train: 1a42f4f7d3260d0b97565ed6b2add408aec72cb4
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: