Closed Bug 1013738 Opened 10 years ago Closed 7 years ago

[Messages] [Contacts] Sending a message in Contacts app will go the Messages inbox first and then go to message composer

Categories

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

Product:
Firefox OS Graveyard
Component:
Gaia::SMS
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(tracking-b2g:backlog, b2g-v2.0 affected, b2g-v2.0M affected, b2g-v2.1 affected, b2g-v2.2 affected)

Status:
RESOLVED WONTFIX
Project Flags:
tracking-b2g backlog
Tracking Flags:
Tracking Status
b2g-v2.0 --- affected
b2g-v2.0M --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected

People

(Reporter: Omega, Unassigned)

References

Details

(Whiteboard: [sms-most-wanted]) 

[Steps To Reproduce]
1. Launch Contacts.
2. Tap a contact (with phone number).
3. Tap the Send Message button next to its phone number
 
[Actual Result]
It goes to Messages app inbox first, and then goes to create a new message.

[Expected Result]
It creates a new message directly.

Device: Helix
OS Version: 1.5.0.0-prerelease
Platform Version: 31.0a1
Build Identifier: 20140416040204
Git Commit Info: 2014-05-21 02:20:18
I think we have another bug about this.

Anyway, will be probably easier once we have bug 881469.
I was able to repro this issue on Flame 2.2 Master (319mb)(Kitkat Base)(Full Flash) and Flame 2.1 (319mb)(Kitkat Base)(Full Flash)

Result: Sending a message in either call log or Contacts app, opens the list of messages first and then goes to the "New message" screen

Environmental Variables:
Device: Flame 2.2 Master (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141023040204
Gaia: 27a1d1baaa8e375b70e043efee67d5f2206c330b
Gecko: 88adcf8fef83
Gonk: 05aa7b98d3f891b334031dc710d48d0d6b82ec1d
Version: 36.0a1 
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

--------------------------------------------------------------------------------------------

Environmental Variables:
Device: Flame 2.1 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141023001201
Gaia: 1e48e3e40e0780c0cd07a3457e5fe2efeeb542d1
Gecko: 09fb60a37850
Gonk: 05aa7b98d3f891b334031dc710d48d0d6b82ec1d
Version: 34.0 
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.1: --- → affected
status-b2g-v2.2: --- → affected
Flags: needinfo?(dharris)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
blocking-b2g: --- → 2.0M?
blocking-b2g: 2.0M? → 2.2?
Triage:
Polish issue. Affect user experience, suggest to fix on 2.2.
I'm not sure whether it's easy or not. We can try easy stuff and see if this works. If we need to do more changes to make it work properly (especially: "on demand" lazy loading), I'm no sure we'll have the resource to work on this in the 2.2 timeframe.
Depends on: 1009545
triage: non-blocking, but put into backlog as this is something we want to improve.
blocking-b2g: 2.2? → backlog
Just want to mention this bug is now more apparent because we wait a longer time before switching after the launch time performance work.
Whiteboard: [sms-most-wanted]
blocking-b2g: backlog → ---
tracking-b2g: --- → backlog
Priority: -- → P1
Mass closing of Gaia::SMS bugs. End of an era :(
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Mass closing of Gaia::SMS bugs. End of an era :(
You need to log in before you can comment on or make changes to this bug.