Hello button turns blue without anyone joining the conversation

RESOLVED FIXED

Status

www.mozilla.org
Pages & Content
RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: avaida, Unassigned)

Tracking

Production

Firefox Tracking Flags

(firefox38.0.5 affected, firefox39 affected, firefox40 affected, firefox41 affected)

Details

Attachments

(1 attachment)

Created attachment 8625282 [details]
screenshot from Windows 10 (x64)

Reproducible on:
* Release 38.0.6 (20150605094246)
* Beta 39.0b7 (20150618135210)
* Aurora 40.0a2 (2015-06-22)
* Nightly 41.0a1 (2015-06-21)

Affect platforms:
Windows 10 (x64), Windows 7 (x64), Ubuntu 14.04 (x86), Mac OS X 10.9.5

Steps to reproduce:
1. Launch Firefox.
2. Click the Hello button from the toolbar and select "Start a conversation".
3. Click the "Copy Link" button from the conversation panel.
4. Check the first-use tooltip (titled "No need to wait around") and check out the color of the Hello button from the toolbar.

Expected result:
According to the tooltip, the button does _NOT_ turn blue until someone joins the conversation.

Actual result:
The button turns blue as soon as the conversation room is opened.

Additional notes:
* This does not seem to be a regression as I managed to replicate it way back on older builds where this feature was implemented.
* It's reasonable to assume that this might simply be an inconsistency or discrepancy between the expected result and what the tooltip displays on first use.
Probably a ui-tour bug in the first instance.
Component: Client → Tours
Product: Loop → Firefox
Just to confirm Mark, are you saying that the copy is wrong? Moving to www.mozilla.org as that's what I understand.
Blocks: 1084082
Component: Tours → Pages & Content
Product: Firefox → www.mozilla.org
Version: unspecified → Production
This string is being fixed for Firefox 40, thanks.

Updated

2 years ago
Blocks: 1178217
No longer blocks: 1084082
Resolving as this was fixed in bug 1178217
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.