Closed
Bug 870120
Opened 11 years ago
Closed 11 years ago
[SMS] maxSegmentsInfo no longer working with new MMS compatible composer
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect, P1)
Tracking
(blocking-b2g:leo+, b2g18 fixed)
Tracking | Status | |
---|---|---|
b2g18 | --- | fixed |
People
(Reporter: danheberden, Assigned: gnarf)
References
Details
Attachments
(3 files)
_mozMobileMessage.maxSegmentsInfo no longer working with new MMS compatible composer - this should be mocked in tests and have tests written to verify its operation.
Reporter | ||
Updated•11 years ago
|
Blocks: mms-userstories
Priority: -- → P1
Whiteboard: dev-branch
Target Milestone: --- → 1.1 CS (11may)
Updated•11 years ago
|
Whiteboard: dev-branch → dev-branch [NO_UPLIFT]
Reporter | ||
Comment 1•11 years ago
|
||
related: https://bugzilla.mozilla.org/show_bug.cgi?id=865411
Reporter | ||
Comment 2•11 years ago
|
||
this was raised from https://github.com/mozilla-b2g/gaia/pull/9385#issuecomment-17627296
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(aymanmaat)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → gnarf37
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(aymanmaat)
Comment 3•11 years ago
|
||
The max-lenght is not working, so you can type more text if you want despite of reaching the max number of characters.
Comment 4•11 years ago
|
||
Here we have 2 things to fix: - Fix Tests - Fix the max-lenght issue
Updated•11 years ago
|
blocking-b2g: --- → leo+
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Updated•11 years ago
|
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 6•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Whiteboard: dev-branch [NO_UPLIFT] → [NO_UPLIFT]
Assignee | ||
Comment 7•11 years ago
|
||
Attachment #748301 -
Flags: review?(fbsc)
Comment 8•11 years ago
|
||
The max length work should be removed with the MMS stuff anyway, that was the plan from the start. With MMS, AFAIK we should not prevent the user from adding more characters and convert the message to MMS instead, so this is a completely different use case, and should be done again from the ground up. As I said, this was the plan.
Comment 9•11 years ago
|
||
> With MMS, AFAIK we should not prevent the user from adding more characters
> and convert the message to MMS instead,
True.
Comment 10•11 years ago
|
||
Comment on attachment 748301 [details] [diff] [review] https://github.com/bocoup/gaia/pull/11 r+ for this patch, but consider whether you could just switch the keydown handler to keypress. I also wonder whether the composeLockCheck() function should actually set locked to false, or if it should just leave that for the composeCheck() function to do. (Unless no 'input' event is generated on backspace.)
Attachment #748301 -
Flags: review?(fbsc) → review+
Assignee | ||
Updated•11 years ago
|
Whiteboard: [NO_UPLIFT] → [NO_UPLIFT] dev-branch
Assignee | ||
Comment 11•11 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/ac229186a02a05e1e0cd998fff0ad7511bf30a63
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Whiteboard: [NO_UPLIFT] dev-branch → [NO_UPLIFT]
Assignee | ||
Updated•11 years ago
|
Whiteboard: [NO_UPLIFT]
You need to log in
before you can comment on or make changes to this bug.
Description
•