Closed
Bug 1192817
Opened 9 years ago
Closed 8 years ago
Conversation window changes height if link-creator reopens the same conversation from hello panel that he is in
Categories
(Hello (Loop) :: Client, defect, P4)
Hello (Loop)
Client
Tracking
(firefox41 affected, firefox42 affected)
RESOLVED
INVALID
People
(Reporter: bmaris, Unassigned)
Details
(Whiteboard: [context bug])
Attachments
(1 file)
1.91 MB,
image/gif
|
Details |
Affected builds: - latest Aurora 41.0a2 - latest Nighty 42.0a1 Affected OS`s: - Windows 7 64-bit - Ubuntu 14.04 32-bit - Mac OS X 10.10.4 STR: 1. Start Firefox 2. Click Hello icon 3. Click Get started 4. Visit a webpage (eg: https://www.mozilla.org/en-US/firefox/hello/) 5. Click Hello icon 6. Tick 'Let`s talk about...' checkbox 7. Start a conversation 8. Click Hello icon 9. Click the same conversation that is running Expected results: Conversation window is focused but nothing happens. Actual results: Conversation window changes height, making context and video area smaller. Chat area is not affected, typing something in chat makes the conversation window to it`s original state. Notes: - Gif attached showing the issue. - This is a recent regression:
Reporter | ||
Comment 1•9 years ago
|
||
(In reply to Bogdan Maris, QA [:bogdan_maris] from comment #0) > - This is a recent regression: This is _not_ a recent regression, it was introduced after moving context from bug 1171940.
Updated•9 years ago
|
Rank: 45
Flags: qe-verify+
Priority: -- → P4
Whiteboard: [context] → [context bug]
Comment 2•8 years ago
|
||
Bogdan: if I understand this bug correctly, is this no longer possible to reproduce in the new product experience.
Flags: needinfo?(bogdan.maris)
Reporter | ||
Comment 3•8 years ago
|
||
You are correct, once we enter one conversation, it's not possible to start a new one, only if detaching conversation window, see bug 1241427. Then things really start to get messy. Closing this as Invalid.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(bogdan.maris)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•