Closed
Bug 1197562
Opened 9 years ago
Closed 9 years ago
Sharing the FTE URL directly via Hello can disrupt tour flow
Categories
(Firefox :: Tours, defect)
Tracking
()
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
firefox43 | --- | affected |
People
(Reporter: agibson, Unassigned)
References
Details
Attachments
(1 file)
(deleted),
image/png
|
Details |
In Bug 1190716 we are implementing the full interactive Hello FTU for Firefox 40. Initially we thought in-product changes we're going to be disruptive to the FTU flow, however it was then decided this was not the case.
I'm filing this bug so it's on record. I don't think there's much we can do about it in regard to Firefox 40, but it's something we should think about for the future.
When the user starts their first Hello conversation, they have the option to tick a check box that says "Let's talk about this page"
If they check the box, it shared the Hello FTU link directly with the link clicker who received the call.
If that person has never launched the Hello before, they will be taken directly into the FTU when clicking the link (assuming they are using Firefox).
This presents a problem however, in that they have never clicked the "Get Started" button before landing on the FTU page. This means when landing on the FTU, the Hello panel opens (see screenshot), but when they click "Get Started", the panel closes and nothing happens. The reason is that this is usually when Firefox opens, the FTU page - but here it is already open.
In order to start the FTU, the user must manually click the Hello icon a second time to start the first step of the tour.
I don't know how people feel about this bug in terms of severity, but I'm opening it for discussion.
Reporter | ||
Comment 1•9 years ago
|
||
Ok. done a bit of discovery and found we can use the following meta tag, so the shared link goes to the product page. Win!
<meta property="og:url" content="https://www.mozilla.org/firefox/hello/">
Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•