Closed Bug 1100284 Opened 10 years ago Closed 10 years ago

Loop rooms shouldn't allow opening the same room more than once

Categories

(Hello (Loop) :: Client, defect, P1)

defect
Points:
3

Tracking

(firefox35 verified, firefox36 verified)

VERIFIED FIXED
mozilla36
Iteration:
36.3
Tracking Status
firefox35 --- verified
firefox36 --- verified
backlog Fx35+

People

(Reporter: standard8, Assigned: mikedeboer)

References

Details

(Whiteboard: [rooms])

Attachments

(2 files, 2 obsolete files)

Currently, if I select a room twice in the panel, then the room opens and connects to itself. Really, we should focus the existing window.
Assignee: nobody → mdeboer
Status: NEW → ASSIGNED
Iteration: --- → 36.3
Points: --- → 3
Flags: qe-verify+
Flags: needinfo?(mmucci)
Flags: firefox-backlog+
Added to IT 36.3
Flags: needinfo?(mmucci)
Well, this seems to get us there, except for detached windows... but that's a bug in Social code.
Attachment #8524739 - Flags: review?(standard8)
Attachment #8525429 - Flags: review?(mixedpuppy) → review+
Comment on attachment 8524739 [details] [diff] [review] Patch 1: use a more canonical window ID for chat windows On the outset it looks fine, but I'm not really familiar with this code, probably better to get someone else to review. My initial question is whether gLastWindowId is still necessary at all.
Attachment #8524739 - Flags: review?(standard8) → feedback+
Fixed a whoopsie... Carrying over r=mixedpuppy. Thanks much, Shane!
Attachment #8525429 - Attachment is obsolete: true
Attachment #8525970 - Flags: review+
Attachment #8524739 - Flags: review?(standard8)
Attachment #8524739 - Attachment is obsolete: true
Attachment #8524739 - Flags: review?(standard8)
Attachment #8525975 - Flags: review?(standard8)
backlog: --- → Fx35+
Priority: -- → P1
Whiteboard: [rooms]
Comment on attachment 8525975 [details] [diff] [review] Patch 1.1: use a more canonical window ID for chat windows Review of attachment 8525975 [details] [diff] [review]: ----------------------------------------------------------------- This seems reasonable. rs=me ::: browser/components/loop/MozLoopService.jsm @@ +761,5 @@ > openChatWindow: function(conversationWindowData) { > // So I guess the origin is the loop server!? > let origin = this.loopServerUri; > + // Try getting a window ID that can (re-)identify this conversation, or resort > + // to a globally unique one as a lasy resort. Typo: s/lasy/last/ @@ +765,5 @@ > + // to a globally unique one as a lasy resort. > + // XXX We can clean this up once rooms and direct contact calling are the only > + // two modes left. > + let windowId = ("contact" in conversationWindowData) ? > + conversationWindowData.contact._guid : Perhaps the guid should become a public property (i.e. drop the _ prefix) in the future?
Attachment #8525975 - Flags: review?(standard8) → review+
(In reply to Matthew N. [:MattN] (UTC+1 until Nov. 22; away Nov. 14-19) from comment #7) > Typo: s/lasy/last/ Fixed. > Perhaps the guid should become a public property (i.e. drop the _ prefix) in > the future? Myeah, that's prolly a good idea. But that would require a DB migration, though. :/ Pushed to fx-team as: https://hg.mozilla.org/integration/fx-team/rev/a7621853f055 https://hg.mozilla.org/integration/fx-team/rev/a46accc80752
https://hg.mozilla.org/integration/fx-team/rev/e8f45cf7b043 https://hg.mozilla.org/integration/fx-team/rev/c773c6be9270 Updated to resolve xpcshell failure (_guid was undefined, so fallback to last window id) r=abr on IRC Tested locally - lets you in twice without the patch; ignores second attempt to join with this patch. Mike: just double-check when you get a chance. (I added "|| gLastWindowId++" after "....contacts._guid")
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla36
(In reply to Carsten Book [:Tomcat] from comment #13) > https://hg.mozilla.org/mozilla-central/rev/33a80305f1b4 > https://hg.mozilla.org/mozilla-central/rev/f5c0481fe56b Is test coverage sufficient or will this need further test coverage?
Flags: in-testsuite+
Comment on attachment 8525970 [details] [diff] [review] Patch 2.1: also support detached chat windows in duplicate chat window handling Approval Request Comment [Risks and why]: Loop rooms code needed for 35 pref-on Connecting a call to yourself is both confusing and useless (and causes other potential problems). [String/UUID change made/needed]: none
Attachment #8525970 - Flags: approval-mozilla-aurora?
Attachment #8525975 - Flags: approval-mozilla-aurora?
Flags: needinfo?(mdeboer)
Attachment #8525970 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Attachment #8525975 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Flags: in-moztrap-
I was able to reproduce this issue on Firefox 36.a1 (2014-11-23) using Windows 7 x64. Verified fixed on latest Firefox 36.0a2 (2014-12-17) and Firefox 35 Beta 4 (20141216120925) using Windows 7 x64 and Ubuntu 14.04 x86.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: