Closed Bug 1238063 Opened 8 years ago Closed 8 years ago

[Messages] Copying text and pasting it in another message is not shown correctly

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1207083

People

(Reporter: isabel_rios, Unassigned)

Details

[Procedure]
1. Compose an sms and send it
2. Open the sms and long tap on the text
3. Select the option Select Text
4. Tap on the left icon to select all text
5. Tap on copy icon
6. Go back and tap on create new message
7. Long tap on the Message field to get the copy icon shown
8. Tap on it to copy the text
9. Check if the text is correctly pasted

[Actual] 
Please see video file attached, the pasted text shows some squares and and the text field is not correctly scrolled.
Please see video file attached (wrong): https://youtu.be/MS1d36XNMP4

[Expected]
The text is correctly pasted.

Note: if instead of tapping on select all text in step 4, the copy icon is tapped, then the copy and paste functionality works fine. Please see video file attched (correct) : https://youtu.be/1VG_Fpx6gR4


Seen on Flame 2.6:
Build ID               20160108043727
Gaia Revision          62900f1e42d596c3faa2787a8bd18a8be034b558
Gaia Date              2016-01-07 14:37:35
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/d4213241bb796fdfa7a5ad4f1989e97b44474364
Gecko Version          46.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.worker.20160108.045817
Firmware Date          Fri Jan  8 04:58:29 UTC 2016
Bootloader             L1TC000118D0

This is also happening on Aries 2.6
This is still the same issue with the rich copy/paste functionality that we don't support.

We should likely dupe to bug 1207083, what do you think ?
Ah ok, sorry I have still to get up to date with this functionality and how it is working so far.
Lets dup on that bug then.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.