Closed
Bug 878603
Opened 11 years ago
Closed 10 years ago
[sms] Always show counter of available characters for current amount of sms
Categories
(Firefox OS Graveyard :: Gaia::SMS, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: aryx, Assigned: ankit93040)
Details
(Whiteboard: [g+][LibGLA, Dev, B] )
Attachments
(2 files, 1 obsolete file)
Bug 813689 implemented the SMS character counter which gets shown if there are only 10 or less characters for the first SMS left. It won't go away if you have still 145 characters for the second SMS. 10 characters are nearly always too few characters to complete a started sentence, there are words longer than that e.g. in German. With a counter which is always shown, I have absolutely no problems to write everything I want in one SMS if I want to and use between 158 to 160 characters (the maximum for one SMS), combined by the possibility to choose one's wording. Android does it similar, but that's also the reason why its SMS app always frustated me.
Comment 1•11 years ago
|
||
Ayman, do you think we should try to display the character counter earlier?
Flags: needinfo?(aymanmaat)
Comment 2•11 years ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #1) > Ayman, do you think we should try to display the character counter earlier? Well i am sat here in Berlin, Germany and all the SIMs and Devices I have access to start the countdown from the last 10 characters of the first packet ...and i have certainly never heard of this being a problem for anyone i know here. That said if there is enough demand form users I would be happy to underwrite extending the counter's visibility period so that it is triggered when the last (say) 20 characters of the first packet is reached... but we don't want the counter to be permanently visible on the screen as soon as the user starts to type. We are attempting to reduce the amount of data (noise) that is displayed by the message app and having the counter permanently visible is not moving us towards that.
Flags: needinfo?(aymanmaat)
Assignee | ||
Comment 3•11 years ago
|
||
Hi Ayman As per your suggestion, I think its a good idea to notify the user from 20 charaters. I am taking up with these issue. I ll upload the patch soon. I am not able to assign these issue to myself please assign these issue to me.
Comment 4•10 years ago
|
||
Ayman, I just want to double check with you that we can make this change now, or do you prefer to have some more input first?
Assignee: nobody → ankit93040
Flags: needinfo?(aymanmaat)
Assignee | ||
Comment 5•10 years ago
|
||
Instead of "Message" we can easily do "type your Message". What else do you expect?
Assignee | ||
Comment 6•10 years ago
|
||
Sorry for the above comments.. It's by mistake.. What I have understood is that instead of showing the number of characters available from 10 we should show it from 20. That is where the progress has stopped. i have done till that & I think that's a good idea as in completing a message with 10 characters is very difficult.
Comment 7•10 years ago
|
||
ankit: please move forward and provide a patch, Ayman will be here this week so I'll be able to ask him directly.
Assignee | ||
Comment 8•10 years ago
|
||
Please have a look at the patch
Attachment #8356487 -
Flags: review?(felash)
Attachment #8356487 -
Flags: feedback?(aymanmaat)
Comment 9•10 years ago
|
||
Comment on attachment 8356487 [details] [diff] [review] bug878603.patch Review of attachment 8356487 [details] [diff] [review]: ----------------------------------------------------------------- The patch looks good, but you need to: * update the unit tests (they're failing with your patch) * create a pull request * if you want to attach a patch, you need to generate it using `git format-patch -U8 <reference_commit>` Thanks!
Attachment #8356487 -
Flags: review?(felash)
Attachment #8356487 -
Flags: review-
Attachment #8356487 -
Flags: feedback+
Assignee | ||
Comment 10•10 years ago
|
||
Hey Julien thanks for feedback. I ll create a pull requset & upload!
Comment 11•10 years ago
|
||
Comment on attachment 8356487 [details] [diff] [review] bug878603.patch Patch looks great to me form a UX PoV. Thanks for the work :)
Flags: needinfo?(aymanmaat)
Updated•10 years ago
|
Attachment #8356487 -
Flags: feedback?(aymanmaat) → feedback+
Assignee | ||
Comment 12•10 years ago
|
||
thanks for the feedback. I ll update the unit test & create a pull request for the same.
Comment 13•10 years ago
|
||
Hi Julienw, Please find the updated pull request with changes and provide your feedback. Thanks,
Attachment #8360362 -
Flags: review?(felash)
Comment 14•10 years ago
|
||
Comment on attachment 8360362 [details]
Pointer to Pull Request
Comments on github
please request review again once it's ready, I'm confident next one will be r+!
Attachment #8360362 -
Flags: review?(felash)
Comment 15•10 years ago
|
||
Hey Julienw, Please find the updated pull request. Thanks
Attachment #8360362 -
Attachment is obsolete: true
Attachment #8360862 -
Flags: review?(felash)
Comment 16•10 years ago
|
||
Comment on attachment 8360862 [details]
Pointer to Pull Request
r=me thanks !
I'll commit it myself
Attachment #8360862 -
Flags: review?(felash) → review+
Comment 17•10 years ago
|
||
master: a3464e77aaee2cceb6f0050c203c7c4f53fba3c0
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 18•10 years ago
|
||
Thanks Julien
Assignee | ||
Updated•10 years ago
|
Whiteboard: [g+]
Assignee | ||
Updated•10 years ago
|
Whiteboard: [g+] → [g+][LibGLA, Dev, B]
You need to log in
before you can comment on or make changes to this bug.
Description
•