1160283 - [SMS] [Text Selection] Attachments are not inserted at the current location of the cursor

Status: RESOLVED DUPLICATE of bug 1154170

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

Description

[Joshua Mitchell (Inactive)]

Attachment: logcat_20150430_1242.txt

Description:
When the user selects in the middle of a block of text in the message body and selects the attach function they might expect the attachment (when appropriate) to appear at the location of the cursor. A common use-case would be a user typing a description of a picture they intend to insert so that the appropriate text will appear below it.
The attachment is able to have text inserted after it by attaching it, and then setting the cursor below it and typing. This indicates that the attachment is able to have text above and below it as you would have when inserting it in a block of text.


Repro Steps:
1) Update a Flame to 20150430010201
2) Launch Messages app and compose a new message
3) Type several lines of text and then tap in the middle to set the cursor there
4) Tap the attachment icon and attach a picture


Actual:
The attachment is added to the end of the message field


Expected:
The attachment is inserted where the cursor is currently located


Environmental Variables:
Device: Flame 3.0
Build ID: 20150430010201
Gaia: db8ea705c0fd1b1684807f5a8e837bb9a36a6f96
Gecko: 4b9b12c248dc
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 40.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0



Repro frequency: 6/6
See attached: logcat, video clip: http://youtu.be/qNg810r4s1E

Comment 1

[Joshua Mitchell (Inactive)]

This issue also reproduces in Flame KK 2.2; text selection is not supported prior to that

Device: Flame 2.2 (KK - Nightly - Full Flash - 319mem)
Build ID: 20150429002501
Gaia: 1b7aa7e60788668ed09abf76022dfa231dbe88d4
Gecko: d38ff4717f39
Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429
Version: 37.0 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Comment 2

[Oleg Zasypkin [:azasypkin]]

Thanks for reporting! Looks like a dupe of bug 1154170.