Closed
Bug 1131607
Opened 9 years ago
Closed 9 years ago
[Loop] It's possible join in a room via Standalone UI, when another communication is established in other room, from the same device.
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: javier.deprado, Assigned: jaoo)
Details
(Whiteboard: [Room1.1.1_TestRun2][Not in 1.1.1])
Attachments
(1 file)
ENV: FireE v2.0 comercial version Flame v2.0 flame-KK.user.v2.0.188based.B-171.Gecko-2b4455b.Gaia-2989f2b Loop versión 1.1.1/253ebde STR: 1.- From Desktop share Room_D vía email with fireE user. 2.- From fireE, join in a Room_1 (shared with flame user), selecting FRONT camera. 3.- Press home button, open email app, and via Standalone UI, join in a Room_D shared from Desktop, selecting BACK camera. ACTUAL RESULT: It is possible to join to Room_D, without closing Room_1 communication. (and obviously, several side effects happen) EXPECTED RESULT: Some kind of message should be shown trying to join to a second Room_D, like "You cannot join to the room because there is another room running".
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8562116 -
Flags: feedback?(borja.bugzilla)
Assignee | ||
Comment 2•9 years ago
|
||
(In reply to José Antonio Olivera Ortega [:jaoo] from comment #1) > Created attachment 8562116 [details] [review] > Pointer to Github PR > https://github.com/mozilla-b2g/firefoxos-loop-client/pull/566 These are the FxOS Hello app bits. Some work in the standalone client is needed.
Updated•9 years ago
|
Attachment #8562116 -
Flags: feedback?(borja.bugzilla) → review+
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → josea.olivera
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•9 years ago
|
||
Landed in master branch at: https://github.com/mozilla-b2g/firefoxos-loop-client/commit/b80233144917468737b3f211e63785e87157b1f8
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•9 years ago
|
Whiteboard: [Room1.1.1_TestRun2] → [Room1.1.1_TestRun2][Not in 1.1.1]
You need to log in
before you can comment on or make changes to this bug.
Description
•