Closed
Bug 1003074
Opened 11 years ago
Closed 11 years ago
[VR][Messaging] When user writes subject in different lines, user can't see "enter" inserted in subject.
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: lolimartinezcr, Unassigned)
References
Details
Tested
Hamachi
1.5
Gecko 177f146
Gaia 4788795
Reproducible: 100%
STR:
1) Tap message aplication.
2) Tap New message.
3) Tap Setting.
4) Tap "Add subject"
5) Write subject in differents lines.
6) Write body.
7) Write "to" and send message.
Actual result:
MMS sent and in subject *can't* see different lines.
Expected result:
MMS sent and in subject can see different lines. . (I have spoken with Vicky and she have confirmed it).
Reporter | ||
Updated•11 years ago
|
blocking-b2g: --- → 2.0?
Comment 1•11 years ago
|
||
Probably a regression from bug 949457.
Comment 2•11 years ago
|
||
No, sorry, I misread the bug, putting back the original blocks.
Comment 3•11 years ago
|
||
I thought that this was the correct behaviour, according to the spec FFOS_MessagesApp_V1.3_20131125_V8.0.pdf (page 12) in https://mozilla.app.box.com/s/0u4jt353ei9ov2c150ip/1/1170795225/11918301182/1
"There is no concept of new line in a subject, however the new line key will be available and selectable from the keyboard therefor:upon selection of new line key on keyboard.
The interface will allow a new line to be entered into the subject string and this will be presented as a new line within the subject input fieldupon select send when a subject contains a new line- Replace all ‘new lines’ that are present in the subject string with ‘space’.
There is no need to notify the user that ‘new lines’ have been replaced with ‘space’ because basically the integrity of the message the subject string is attempting to convey is not lost or altered if we replace ’new line’ with ’space’. A notification itself might well = noise so we are comfortable operating with out one. "
I checked and commented with Borja about it in https://bugzilla.mozilla.org/show_bug.cgi?id=949457#c33
and as far as I remenber we agreed in following the spec, so I should close the bug as Invalid
Reporter | ||
Comment 4•11 years ago
|
||
(In reply to Maria Angeles Oteo (:oteo) from comment #3)
> I thought that this was the correct behaviour, according to the spec
> FFOS_MessagesApp_V1.3_20131125_V8.0.pdf (page 12) in
> https://mozilla.app.box.com/s/0u4jt353ei9ov2c150ip/1/1170795225/11918301182/1
>
> "There is no concept of new line in a subject, however the new line key will
> be available and selectable from the keyboard therefor:upon selection of new
> line key on keyboard.
>
> The interface will allow a new line to be entered into the subject string
> and this will be presented as a new line within the subject input fieldupon
> select send when a subject contains a new line- Replace all ‘new lines’ that
> are present in the subject string with ‘space’.
>
> There is no need to notify the user that ‘new lines’ have been replaced with
> ‘space’ because basically the integrity of the message the subject string is
> attempting to convey is not lost or altered if we replace ’new line’ with
> ’space’. A notification itself might well = noise so we are comfortable
> operating with out one. "
>
> I checked and commented with Borja about it in
> https://bugzilla.mozilla.org/show_bug.cgi?id=949457#c33
> and as far as I remenber we agreed in following the spec, so I should close
> the bug as Invalid
For this reason, i change status to RESOLVED INVALID
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Updated•11 years ago
|
blocking-b2g: 2.0? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•