Closed
Bug 1070753
Opened 10 years ago
Closed 10 years ago
Standalone Client's title is still "Loop"
Categories
(Hello (Loop) :: Client, defect)
Hello (Loop)
Client
Tracking
(firefox35 fixed)
Tracking | Status | |
---|---|---|
firefox35 | --- | fixed |
People
(Reporter: standard8, Assigned: jaws)
References
Details
User Story
The title of the standalone link-clicker UI is still just "Loop". Should change to "Firefox Hello - <status>
Attachments
(1 file)
3.04 KB,
patch
|
dmosedale
:
review+
|
Details | Diff | Splinter Review |
The title of the standalone link-clicker UI is still just "Loop".
We should either change it to "Firefox WebRTC" (or product name), or do we want some combination of, for example "In call - Firefox WebRTC", with the "In call" part updating appropriately.
Darrin, any thoughts here?
Flags: needinfo?(dhenein)
Comment 1•10 years ago
|
||
I would reverse the order, so it reads "<product name> - <status>"... as for what product name we are using when/where, i defer to Arcadio.
Flags: needinfo?(dhenein) → needinfo?(alainez)
Comment 2•10 years ago
|
||
Arcadio - just checking that on Link clicker we want to say "Firefox Hello - <status>" versus <Hello - <status>".... so that folks receiving the link and clicking on it see our brand and product name??
Your call - just adapt user story if just product name is better.
User Story: (updated)
Comment 4•10 years ago
|
||
Adding NI to Arcadio for confirmation.
Comment 5•10 years ago
|
||
Just talked to Arcadio who confirmed we can use the "Firefox Hello" name.
This bug is then to replace "Loop" by "Firefox Hello - <status>".
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → jaws
Status: NEW → ASSIGNED
Iteration: --- → 35.3
Points: --- → 1
Flags: qe-verify-
Flags: in-testsuite-
Flags: firefox-backlog+
Assignee | ||
Comment 7•10 years ago
|
||
What are we going to put for the <status>? I assume it is things like {"Start Conversation", "In Conversation", "Conversation Ended"}, but we don't have all of those strings yet.
The closest we have is "Start conversation?", (missing), and "Your conversation has ended."
Can we go with just putting the product name and no <status> for now? So just "Firefox Hello"?
Flags: needinfo?(rtestard)
Assignee | ||
Comment 8•10 years ago
|
||
This patch changes the title of the page to Firefox Hello but leaves off the <status> based on my above comment. I'd rather that we land this now and then we can determine if a follow-up is necessary to add the <status> bits.
I removed the title from about:looppanel since no reasonable person will be loading about:looppanel directly.
Attachment #8502765 -
Flags: review?(dmose)
Comment 9•10 years ago
|
||
r+ conditional on making the change in the .jsx and then regenerating the js file from that. A unit test here is probably not worth the effort at this moment.
Flags: needinfo?(rtestard)
Updated•10 years ago
|
Attachment #8502765 -
Flags: review?(dmose) → review+
Updated•10 years ago
|
Flags: needinfo?(rtestard)
Assignee | ||
Comment 10•10 years ago
|
||
Whiteboard: [fixed-in-fx-team]
Comment 11•10 years ago
|
||
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #7)
> What are we going to put for the <status>? I assume it is things like
> {"Start Conversation", "In Conversation", "Conversation Ended"}, but we
> don't have all of those strings yet.
>
> The closest we have is "Start conversation?", (missing), and "Your
> conversation has ended."
>
> Can we go with just putting the product name and no <status> for now? So
> just "Firefox Hello"?
Yes agreed. I'll create a separate bug for the status once we have the link clicker UI finalized with all call states (we don't have call failed currently)
Flags: needinfo?(rtestard)
Comment 12•10 years ago
|
||
Bug 1081029 now created to track call status implementation in the title.
No longer blocks: 1081029
Comment 13•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → mozilla35
status-firefox35:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•