Closed
Bug 1169632
Opened 9 years ago
Closed 9 years ago
Conversation name vanishes if the window is detached by dragging
Categories
(Hello (Loop) :: Client, defect, P4)
Hello (Loop)
Client
Tracking
(firefox43 verified)
Tracking | Status | |
---|---|---|
firefox43 | --- | verified |
People
(Reporter: adalucinet, Assigned: standard8)
Details
(Whiteboard: [conversatio] [bug])
Attachments
(1 file)
Reproducible on 39.0b1 build 2 (Build ID: 20150523155636) Affected platforms: Windows 7 64-bit, Mac OS X 10.9.5, Ubuntu 14.04 64-bit Steps to reproduce: 1. Start a call. 2. Detach conversation by dragging the window. Expected result: Conversation name is displayed. Actual result: Conversation name is not displayed. Notes: 1. Screencast: https://goo.gl/7KZQMx 2. Browser console output when detaching: 'TypeError: win.gBrowser is null' thrown by ReaderParent.jsm:168:0
Updated•9 years ago
|
Rank: 41
Flags: firefox-backlog+
Priority: -- → P4
Whiteboard: [conversatio] [bug]
Assignee | ||
Comment 1•9 years ago
|
||
I took a quick look at this and it turns out that the drag specific detach code is trying to set the title, but hasn't got the right title. Additionally, the detachChatbox code already has embedded within the facility for setting the title on detach. So I think all we need to do is to remove the broken part of the code.
Attachment #8659800 -
Flags: review?(mixedpuppy)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → standard8
Updated•9 years ago
|
Attachment #8659800 -
Flags: review?(mixedpuppy) → review+
Assignee | ||
Updated•9 years ago
|
Iteration: --- → 43.3 - Sep 21
Points: --- → 2
Comment 3•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/0c7ecbc66443
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox43:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla43
Updated•9 years ago
|
Flags: qe-verify+
Reporter | ||
Comment 4•9 years ago
|
||
Verified fixed with latest 43.0a1 (from 2015-09-15), across platforms [1]. [1] Windows 7 64-bit, Mac OS X 10.9.5 and Ubuntu 12.04 32-bit.
You need to log in
before you can comment on or make changes to this bug.
Description
•